Budget: 700 UAH Deadline: 1 day
$20/hour, contact us
I need a developer who will deploy my WordPress site updates on AWS.
I make changes to the code myself (theme, PHP, templates), you upload them to the AWS server, make a backup before the update, and check that the site works without errors.
Requirements:
Experience with AWS (EC2/Lightsail), Linux, SSH, Git, WordPress.
Task:
Get my files → deploy on AWS → clear cache → check the site.
Reply with:
Experience with AWS+WP, deployment cost, completion time.
I need a person for backup, meaning deployments will be regular, please specify the price for 1 deployment.
Budget: 700 UAH Deadline: 1 day
$20/hour, contact us
Budget: 1000 UAH Deadline: 3 days
Hello. I am ready to take on your project.
I have over 4 years of experience working with AWS, certified as an AWS Certified Solutions Architect.
I propose to build a CI/CD system based on AWS services or we can integrate with your code storage system, for example, GitHub, and use GitHub Actions.
Everything will be automated; you push your code, and the build and deployment process starts, changes go to the environment, this is a rough and simplified explanation.
Such work will take approximately 5-10 hours of work.
Budget: 1500 UAH Deadline: 1 day
Good day. Experience working with web projects - from 2012 to 2019 permanently, then temporarily created websites due to reprofiling. Experience with AWS for 2 years - I have a certificate. 99% DevOps on AWS. Write to me, we will discuss the details.
Budget: 700 UAH Deadline: 1 day
Good day!
I can set up a backup pipeline, deployment, and cache clearing will occur automatically. I have experience with AWS.
Budget: 850 UAH Deadline: 1 day
Hello. I can do both a one-time deployment and set up automation for this process (CI/CD). Experience is present. The cost depends on the time spent. The deployment time depends on the "weight" of the material being deployed, the delivery method, and the performance of the network and server. Plus, the first deployment always takes more time than the subsequent ones. Is the server ready for deployment and is the code already in git? To optimize the process, I also recommend considering a testing environment where updates can be tested before deployment. Because making a backup before deployment takes time + resources. If interested, feel free to reach out. $20/hour.
Budget: 700 UAH Deadline: 1 day
Hello. I have experience as a SysAdmin, DevOps. Available every day. Contact me!
Budget: 700 UAH Deadline: 1 day
Hello.
If it's just deploying changes, I am ready to complete your task.
The price rate for 1 deployment.
Budget: 5000 UAH Deadline: 3 days
Good day, I can offer you CI/CD setup for your project, so you don't have to pay someone for each deployment, everything will be done automatically. After deployment, you can run accessibility tests on the site, and you will be pleased. Feel free to reach out.
Budget: 700 UAH Deadline: 1 day
Good day! I am interested in your project and ready to assist with the regular deployment of updates for the WordPress site on AWS (EC2/Lightsail). I have practical experience in DevOps and working with AWS, Linux, SSH, Git, and WordPress projects, so I guarantee careful and secure deployment.
Cost: 600 UAH per deployment.
I would be happy to collaborate and provide regular support for your site!
Budget: 715 UAH Deadline: 1 day
DevOps with more than 5 years of experience.
17₴ per hour.
For discussion, write in private messages.
I can work with you on a permanent basis.
Budget: 700 UAH Deadline: 1 day
Good day. I can help with this project, I have many years of relevant experience. Feel free to contact me.
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.