Vitalii D.
Winning proposal- Projects 11
- Rating 5.0
- Rating 768
Budget: 8000 UAH Deadline: 5 days
For 15 years I have served VPS customers in the tech support of the hosting provider, so I know how to do this as simple and fast as possible. I will show you what you need. In the day it will be ready.
Budget: 65000 UAH Deadline: 55 days
Congratulations ! Our team is ready to implement your project. For a more accurate assessment, it would be good to get a contact to clarify the details. Details can be discussed individually. We are waiting for your comments! Congratulations to Brille.Dev team!
Budget: 79999 UAH Deadline: 30 days
I understand why you have such difficulties, everything described can be realised, but consider that if you use only 1 server as a dns then the mail may not always "reverse" you need at least 2. Another question about the changes in the ns in the domains, are you also changing them by API?
The price of the project will not be small because there is a lot of work.
Budget: 4000 UAH Deadline: 2 days
Hello to you! He created a similar solution where domain and mail accounts can be managed both through a web interface and through a simple API (LEMP realisation). I’ll tell the VPS provider, I’ll set the server, ready to remotely solve operating problems, support users. Ready to get started immediately after discussing the details. aimed at long-term cooperation.
I am in Chernobyl, a personal meeting is possible.
Proposals concealed
Proposals are currently absent
-
Vitalii D. 15 March 2023Ви ще високонагруженних проектів мабудь не бачили, де кілька мільйонів запитів за хвилину прилітає. I так, 24\7\365 звісно. Для цього дата-центри і будують, в яких ці самы віртуальні сервери і знаходяться.
-
Vitalii D. 16 March 2023Ви трохи до слiв придераэтесь, звiсно вiдома, а якщо я скажу так - зпит на створення запису, то це буде запит чи створення?
-
Ruslan B. 16 March 2023звичайно запит
не виконаються умови або не достатньо прав
від бажання створити є ще крок : дозвіл :)
Current freelance projects in the category DevOps
Updating and migrating Laravel projects to a new server
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.
Transfer email from Google Workspace to another platform
I'm looking for a specialist who can help transfer corporate email from Google Workspace to another email platform. We want to switch because Google Workspace is currently quite expensive for us. We have about 30 users. We haven't finalized which platform to switch to yet, so we would appreciate your recommendations for the optimal option in terms of price, reliability, and convenience. On our side, we are currently considering MXRoute, but we are open to other proposals as well. The main task is to transfer the email with minimal downtime and without losing any messages.