<<<<<<< HEAD
1.- Este repositorio es de código abierto pero de acceso privado, se permite la distribución y/o modificaciones si se hace referencio a la casa matriz del desarrollo de este es software es https://facturaloperu.com
2.- Esta sección de términos y condiciones no puede ser removida al compartir o distribuir el repositorio de alguna forma, de hacerlo, https://facturaloperu.com se reserva el derecho de remover el acceso y limitar el uso a quien lo distribuya de esa forma o a quien se atribuya el desarrollo del mismo.
3.- Si desea distribuir el código fuente como propio, debe tener al menos un 30% de modificaciones en todo el código, y previamente debe validarse dicho % por https://facturaloperu.com
4.- El uso del software a nivel funcional es marca blanca, sin embargo a nivel de distribución del código fuente, debe contener esta sección de términos y condiciones.
5.- https://facturaloperu.com no se hace responsable por los daños o perjuicios del uso del código de este software cuando no ha sido distribuido directamente por https://facturaloperu.com
Windows
Docker - Linux
Docker - Linux - SSL
Valet - Linux
Linux - gestión externa de SSL
Linux - Ubuntu 18 - Docker - SSL opcional
Guia
Script
- Docker - Comandos manuales
- Docker
Manual de usuario
Manual de Tareas Programadas
Manual de Cambio de Entorno (Usuario secundario)
Manual de Pruebas
Descargar colección para Postman
Documentación - Ver json con respuestas
URL
Usuario: admin@gmail.com
Contraseña: 123456
URL
Usuario: demo@gmail.com
Contraseña: 123456
Conexión remota al servidor: Guía
Guía acceso SSH - Putty: Guía
Conexión servidor Winscp: Guía
Montar proyecto en /home: Guía
Documentación del archivo .ENV: Guía
Incrementar recursos - servidor: Guía
Incrementar recursos - aplicación: Guía
Configuracion de correo electrónico emisor: Guía
Configuracion de correo emisor por cliente: Guía
Manual - Cambio de dominio: Guía
Linux - Eliminar temporales: Guía
Linux - Eliminar archivos por extensión: Guía
Configuración servidor alterno SUNAT: Guía
Habilitar debug: Guía
Configuración de API RUC/DNI (APIPERU): Guía
Configuración de tareas programadas (crontab-LAMP): Guía
Guía acceso a base de datos: Guía
Cambiar Contraseña root: enlace
Iniciar servicios docker: Guía
Guía generar backup: Guía
Restauración de Mysql|Docker: Guía
Guía incrementar espacio disco: Guía
Limpiar inodes: Guía
Migración servidor: Guía
Manual de configuración offline: Guía
Habilitar puertos en Google Cloud: Manual
ICBPER en POS: Guía
Acceso red local - laragon: Guía
Procedimiento para solucionar error 1033 SUNAT: Guía
Recreación de documentos: Guía
Manual de cambios privados: Guía
Validador documentos: Guía
- Use Issues como sistema de tickets para añadir sus sugerencias, problemas o inquietudes
- Inconvenientes con facturación serán atendidos con prioridad
- Una vez obtiene acceso al repositorio tendrá un año de vigencia, pasado el año debe renovar su contrato
- Toda instalación es gestionada mediante los canales de Slack
- Nuevas instalaciones o actualizaciones deben ser programadas y gestionadas, para ser ejecutada el mismo día debe haber un problema previo
facturaloperu.com
soporte@facturaloperu.com
wsapp: 930 973 902
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
Already a pro? Just edit this README.md and make it your own. Want to make it easy? Use the template at the bottom!
- Create or upload files
- Add files using the command line or push an existing Git repository with the following command:
cd existing_repo
git remote add origin https://gitlab.com/grcornejoas/pro6.git
git branch -M main
git push -uf origin main
- Invite team members and collaborators
- Create a new merge request
- Automatically close issues from merge requests
- Enable merge request approvals
- Set auto-merge
Use the built-in continuous integration in GitLab.
- Get started with GitLab CI/CD
- Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)
- Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy
- Use pull-based deployments for improved Kubernetes management
- Set up protected environments
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to makeareadme.com for this template.
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
Choose a self-explaining name for your project.
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
If you have ideas for releases in the future, it is a good idea to list them in the README.
State if you are open to contributions and what your requirements are for accepting them.
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
Show your appreciation to those who have contributed to the project.
For open source projects, say how it is licensed.
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
e8375b5ea283762c555a05b5c16771955b9704e2