Budget: 400 EUR Deadline: 4 days
Good day! I can do everything on GitLab as stated in the job description.
There is a server on node.js + cloud DB PostgreSQL
There is a web application on vue.js
Need to set up CI-CD
DEV-> Staging ->live
Need to define, implement, and configure these processes.
Briefly describe the proposed technologies\solutions and approximate cost of work. Additional information can be requested in advance.
Budget: 400 EUR Deadline: 4 days
Good day! I can do everything on GitLab as stated in the job description.
Budget: 220 EUR Deadline: 2 days
Приблизна схема
GIT-- (which branch) --> Builder (use dev stage or live .env depends on branch) -- (which branch) --> server (dev, stage or live depends on branch)
Технологии:
GIT - server version control for CODE
CI/CD - github action/gitlab CI/CD /gitbucket CI/Azuer DevOps .... with their build in CI/CD or Jekins or any Vue.js deploying services (heroku....)
Вартість 220Euro, якщо завдання не буде розширено unit, lint і иому подіьними тестами чи додатковими інтеграціями (сповіщення, sonar,...)
Budget: 150 EUR Deadline: 5 days
Good day, I can set up CI/CD for your application using all the best practices.
I have a few questions:
Where are your repositories located?
Do you already have dev->stage->prod environments set up?
Is it necessary to deploy and configure everything from scratch?
Which Hosting provider do you use?
Does the application use Docker or Kubernetes?
I will provide more details in private.
Budget: 1200 EUR Deadline: 30 days
Hello. I can set up the CI/CD process for you, I have experience in setting up similar processes.
I have a few questions:
- what source control do you use? Where is it hosted? Who has administration rights?
- do you have npm scripts set up for builds?
- do you use containers?
- what live load is expected (ideally look at non-functional requirements)?
- who will be responsible for further support?
- where should the environment be hosted? On-premises or on the cloud? Depending on this, either a cloud solution is proposed or an alternative is formed and the next set of questions is created.
P.S. The deadlines are approximate, as they greatly depend on the project and additional requirements that arise during the process.
Доброго дня!
Яким інструментом потрібно реалізувати? Github, Gitlab, Jenkins ....
Які терміни?
It is necessary to perform the update, transfer, and configuration of Laravel projects to a new server, ensuring stable operation, security, protection against exploits, and correct functioning of all services after migration. 1. Main tasks Prepare the new server for operation. Transfer project files, databases, configurations, and cron jobs. Update server software. Configure a secure environment for Laravel. Check compatibility of PHP, Laravel, Composer packages, and dependencies. Ensure protection against known exploits, malicious requests, and unauthorized access. Set up SSL certificates. Check the functionality of the websites after the transfer. 2. Transfer of Laravel projects For each project, it is necessary to: Transfer project files. Transfer the database. Transfer the .env configuration. Set directory access permissions: storage bootstrap/cache Check functionality: homepage; admin panel; authorization; forms; API; file uploads; email sending; cron jobs; queue workers.3. Security and protection It is necessary to implement basic and application-level protection: close root access via SSH; configure SSH access only via keys; change the default SSH port if necessary; configure the firewall; allow only necessary ports; install Fail2Ban; hide service versions of Nginx/Apache/PHP; restrict access to .env, .git, backup files, log files; set correct file permissions; check projects for malicious files; check Composer packages for known vulnerabilities; update dependencies if it does not break functionality; configure protection against SQL injection, XSS, CSRF, and path traversal; check the correctness of Laravel APP_ENV and APP_DEBUG; set APP_DEBUG=false in production; configure rate limiting for critical endpoints; check access to storage/uploads; configure protection against PHP execution in upload directories; check access rights to admin panels. 4. SSL and domains It is necessary to: Install SSL certificates. Configure automatic SSL renewal. Enable redirect from HTTP to HTTPS. Check the correct operation of websites via HTTPS. 5. Backup It is necessary to configure backup: project files; databases; .env files; uploaded media; cron configurations; Nginx/Apache configurations. Backup should be performed automatically on a schedule. It is preferable to store copies separately from the main server. 6. Post-transfer verification After migration, it is necessary to check: absence of 500/403/404 errors; absence of critical errors in Laravel logs. 9. Result of execution After the work is completed, there should be: Laravel projects successfully transferred to the new server; websites are functioning stably; SSL is configured; the server is protected with basic security settings; access to critical files is restricted; backup is configured; cron and queues are operational; the old server can be turned off after final verification.
We have a dedicated server on Hetzner with a website on Docker (+ Laravel framework) Contact with the developers has been lost Need to: - restore and change server access (probably SSH) - recommend a storage location and set up a full server backup with easy recovery, probably not on Hetzner for security - fix the logo that is not displaying for some reason (it's unclear why the file has become inaccessible) Important - there is no website backup, and there is no room for error. We will only consider experienced specialists.