Без жодних зайвих питань.
Дякую.
It is necessary to deploy a ready-made B2B web project on a new Cloud server
Mirohost MS31 (Ubuntu 22.04 LTS).
Stack: Docker Compose (FastAPI backend + React frontend), nginx
reverse proxy + Let's Encrypt SSL, custom domain.
Scope of work:
— basic OS security (SSH key auth, ufw, fail2ban)
— Docker + docker-compose
— domain connection + SSL Let's Encrypt
— project transfer from GitLab (clone + build + run)
— host nginx + reverse proxy to containers
— cron-backup DB + static
— smoke test according to the checklist (11 scenarios)
— (optional) Cloudflare DDoS protection
— handover documentation
I have a detailed technical specification in Word format (14 pages, all commands
ready for copy-paste, all config files provided). I will send it after
the discussion begins.
Requirements for the performer:
— experience with Ubuntu Server + Docker
— confident knowledge of nginx, Let's Encrypt, ufw, fail2ban
— attention to detail (production server with real clients)
— willingness for retainer support 2-4 hours/month after deployment
In your response, please indicate:
1) Your experience with similar projects
2) Estimated cost of work (fixed)
3) Willingness for further support on retainer
Budget: 5000 UAH Deadline: 5 days
Good day! I can complete the task as I have extensive experience with production, I will set up CI/CD. I will configure backups. I can support the project.
Budget: 2500 UAH Deadline: 3 days
Good day. I am ready to complete your task. Write to me. I have experience working with Docker. Write to me. Thank you.
Budget: 5000 UAH Deadline: 7 days
Good day!
I am responding to your technical specification. The stack and scope of work are familiar to me — this is what I am already doing in production for a real B2B (a network of stores, clients, integrations). Google Drive
1) Experience with similar projects
In production, I support infrastructure on Ubuntu VPS with the same approach as in your specification:
Docker Compose: several services running in parallel — FastAPI (API, webhooks, cron endpoints) + PostgreSQL + separate bots/workers.
FastAPI + React: for example, loyalty-api + web-admin (Vite/React) — front-end build in a container, API via reverse proxy, health checks, deployment script git pull → build → up -d.
Host nginx → containers: public domains (loyalty.*, tg.*) through nginx upstream on 127.0.0.1, HTTPS (Let's Encrypt / certbot), separate locations for API and static files.
Security: checklists for secrets, CORS, closing unnecessary ports from the internet, key rotation; in migration documentation — ufw (22/80/443), SSH, separating public access only through 443.
Git → server: clone/pull from the repository, .env outside of git, recoverable update procedures without downtime "blindly".
Backups + cron: daily PostgreSQL dumps, retention 14–30 days, job logs, separate restore scripts — tested on real data.
Smoke / runbook: health (/health), docker compose ps, nginx -t, typical 502/504 errors, database recovery — documented in runbooks for production.
Operating system: migration plan between hosts (inventory of ports/domains, DNS, certbot, checklists), OPS guide for disk/RAM, autostart docker + nginx after reboot.
This is not a "training" deployment, but production with real users — therefore, I work on the principle: first backup and rollback, then change; after each step — a short check, not "deploy and forget".
Your 14-page specification with ready commands is a convenient format: I usually work the same way (runbook + copy-paste + handover), so I will quickly go through the checklist without improvisation on the server.
Yes, I am ready for a retainer of 2–4 hours/month after deployment:
updates from GitLab (build + restart);
checking backups and disk space;
minor nginx/SSL/cron adjustments;
response to alerts (502, container down, certificate);
a monthly short health report (optional).
Budget: 22000 UAH Deadline: 4 days
Approximately based on your description - 22000 UAH fixed, deadline - up to 4 working days after access and specifications. We can provide support 2-4 hours/month after deployment, preferably with a short response time and a list of responsibilities.
> Experience - Ubuntu Server, Docker Compose, nginx, Let's Encrypt, ufw, fail2ban, backups, post-release checks. We usually handle similar tasks through a checklist, so the production server doesn't rely on magic and coffee, although coffee sometimes works too =)
> Here’s the nuance - if the Word specifications already contain all the commands, I wouldn’t just run them mechanically, but would check the environment variables, container networks, directory permissions, logs, cron-backup, and recovery from backup. Handover documentation is also necessary not just for aesthetics - it saves hours of support later.
> What we need from you - SSH key access, domain or DNS access within the exchange, GitLab access to the repository, environment variables without public disclosure in the chat, database information, and a checklist of 11 scenarios.
> Clarification - Is the database in the compose or separately on the server?
> Clarification - Should the deployment be done with downtime or is there a window when real clients are not working?
> Relevant examples
>> https://business.ingello.com/platforma - corporate platform where stable architecture and operation are important
>> https://business.ingello.com/forma-bpm - business system with processes, roles, and post-launch support
>> https://systems-fl.ingello.com/ua - Ingello Systems for FLH
Budget: 18000 UAH Deadline: 5 days
I already have a practically ready similar solution for the production deployment of a B2B system on Ubuntu with Docker Compose, nginx, SSL, basic security, and backups - it can be quickly adapted to your server and discussed here on the marketplace right now, I'm nearby ))
We can take the job for a fixed price of 18,000 UAH and allocate 5 working days.
With further retainer support of 2-4 hours/month also okay - usually this includes monitoring, updates, minor configuration tweaks, backup checks, and incident response.
Based on experience - we have set up and maintained servers for corporate systems, CRMs, dashboards, services with roles, APIs, domains, SSL, backups, and documentation.
From your specifications, it is clear that the task is not just to install Docker, but to carefully secure the production node - access, domain, build from GitLab, host nginx, SSL, cron backups, smoke tests on 11 scenarios, and handover.
I would simplify it - first check DNS and access, then basic security, then deployment, then backups, then a checklist and a short instruction for the team.
Look, there’s a nuance - it’s preferable to separately agree on the technical window time if there are already real clients.
> I will clarify 2 questions to make the assessment more accurate
>> Is the database already containerized or is it running separately on the server?
>> Is the domain already delegated to Mirohost or Cloudflare?
> Relevant examples
>> https://business.ingello.com/platforma - corporate platform with roles, admin logic, and internal processes
>> https://business.ingello.com/forma-bpm - systems for managing business processes, where stable server performance is important
>> https://business.ingello.com/vorfahr - a SaaS project with a similar approach, where production reliability and scalability are crucial
Main landing page of Ingello for FLH - https://systems-fl.ingello.com/ua
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.
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.
Good day, I need help connecting Google Analytics and CRM through n8n. All settings on the CRM side are done. Now we just need to set up the analytics through n8n to transmit sales events.