- Projects 5
- Rating 5.0
- Rating 748
Budget: 300 UAH Deadline: 1 day
Good day . Great experience – look at the portfolio. Assessment of the cost and deadlines after acquaintance with the TZ.
Budget: 850 UAH Deadline: 3 days
Welcome to Vyacheslav. I shake Yii sites like nuts. If you need my service, please contact me, I'm always in contact.
- Projects -
- Rating -
- Rating 93
Budget: 10000 UAH Deadline: 7 days
Hi, experience working with Yii - 9 years, I work both c backend and frontend, layer and design make for free
Budget: 3000 RUB Deadline: 2 days
ready to perform quickly, experience with YII and the implementation of various API
Budget: 5000 UAH Deadline: 10 days
Hello to you!
Let me present!
My name is Vyacheslav, I am a software engineer with 2 years of experience in creating websites.
Among my skills are:
Deep knowledge of PHP, HTML, CSS, JS, MySQL, PgSQL, AngularJS
If my proposal was interested in you, I am always open to communication. And I will be glad to contribute to your project.
with respect,
by Vyacheslav
Budget: 12000 UAH Deadline: 7 days
Good Morning, ready to complete your order - is the line ready already?
More detail is needed.
Vladislav Cherny
Winning proposal- Projects 67
- Rating -
- Rating 1 365
Budget: 5000 UAH Deadline: 7 days
Great experience of working with Yii2 and various API. Write more in LS. Examples of work will be provided.
Proposals concealed
Proposals are currently absent
-
Viacheslav Bykov
6 December 2018
даю более детальное ТЗ, чтобы оценить сроки и стоимость
https://drive.google.com/open?id=1KBXklq4CLeto96B-pIsWQPuB4zudUvay -
Konstantin Komarov 6 December 2018Здравствуйте, задача интересная, я бы разбил её на компоненты:
1. CRON
2. Управление пользователями
3. Frontend
4. Backend
5. Оповещения по email
6. Динамический IP
Срок: неделя
-
Konstantin Komarov 6 December 2018Вячеслав, цену можно обсудить если моя ставка превышает Ваш бюджет
Current freelance projects in the category PHP
It is necessary to migrate a custom project from CodeIgniter 2 to Laravel 12. I will provide details in private messages.
Project The existing website is developed on Symfony. The project needs to be taken over for support, familiarize with the code, and subsequently carry out improvements. Main tasks Implement all technical recommendations from the SEO specialist according to the provided technical assignment. Make changes to the monument configurator according to a separate list of requirements. Implement the updated website design (layout and integration of the new design). Carry out further technical improvements and support for the website as needed. Expectations from the developer Familiarization with the project structure and codebase. Assessment of costs and timelines for each stage. Adherence to the existing project architecture and quality implementation of changes. Maintaining communication regarding task execution and possible technical solutions.
I want a bot for Telegram. Loading dialogues. With the help of AI, checking for potential lies. A website with advanced features. Registration, API, statistics, etc.
It is necessary to migrate the Opencart online store from PHP 7.4 to PHP 8.x. Currently, the core version is 3.0.3.8. We read that most likely the core will also need to be migrated to version 4.0 and there shouldn't be many difficulties... The functionality is mostly custom, and there are also Simple, OCFilter, Nova Poshta. We are waiting for recommendations and an approximate price. Ideally, someone who has already done similar work.
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.