Budget: 3500 UAH Deadline: 1 day
Good afternoon! I can help find and eliminate the cause of the increase in inodes and occupied space on the hosting.
The number of inodes and the space occupied in GB on the hosting is increasing. We cleared everything on the host, the inodes decreased and the space too, but they started increasing again on their own. We need to find the problem and solve it.
Budget: 3500 UAH Deadline: 1 day
Good afternoon! I can help find and eliminate the cause of the increase in inodes and occupied space on the hosting.
Budget: 1000 UAH Deadline: 1 day
Hello. I will find the source of the inode leak and fix it — sessions, logs, cron, mail queue. Quickly. Access to the hosting is needed.
Budget: 1000 UAH Deadline: 1 day
Hello. I am ready to help. Could you send more detailed information about the website and hosting?
Budget: 700 UAH Deadline: 1 day
👋 Hello! I'm ready to start working right now. I clearly understand the task and have successful experience in implementing exactly such projects (examples are in the reviews). I will complete the task today, quickly and without unnecessary questions. Let's discuss the details and get started! 🚀
Budget: 2000 UAH Deadline: 1 day
Hello.
I can check the hosting, find the source of inode/space growth, and suggest a safe solution.
Usually, the cause is in the cache, logs, temporary files, sessions, backups, cron jobs, or the operation of the CMS/plugins. First, we need to identify the specific folder and process that is recreating the files.
The cost of diagnostics and basic fixes: 2000 UAH.
Deadline: up to 1 day.
To get started, access to the hosting is needed: control panel and, preferably, SSH. If after the check it turns out that the cause is a website infection or a code error, we will separately agree on the scope of the fix.
Budget: 900 UAH Deadline: 2 days
Good day. Write to me, we will discuss all the nuances and find the reason for the increase in inode usage. Thank you.
Budget: 700 UAH Deadline: 1 day
Good evening. I will help find the cause and fix it. I have encountered such problems multiple times. Usually, it is session files or disk cache.
Budget: 2000 UAH Deadline: 2 days
Hello. I will find the reason for the growth of inodes and occupied space on the hosting, even if the problem reappears after cleaning. I will check the logs, cache, temporary files, backups, email, sessions, cron jobs, and processes that create new files, after which I will eliminate the source of the problem and restore order to prevent the growth from recurring. As a result, you will receive not just a cleanup, but a clear understanding of the problem and its solution.
Budget: 2000 UAH Deadline: 3 days
Hello! I have reviewed your project and am ready to start working immediately. I guarantee excellent quality and promptness.
Budget: 700 UAH Deadline: 1 day
Hello!
We are ready to figure it out — we will find out what exactly is generating extra files and eliminate the cause.
Here’s how we see the implementation:
1. Diagnosis — we will check the logs, cache, tmp directories, cron jobs — we will find out what exactly is increasing.
2. Resolution — we clean the source, set up auto-cleaning to prevent it from happening again.
3. Monitoring — we will check after the fix to ensure that it is no longer increasing.
Message us privately — we will consult and sort out the details.
Budget: 1000 UAH Deadline: 1 day
Good day
I have 10 years of experience working in hosting support.
I will solve any task.
Feel free to contact me, I will help you understand what is taking up space and eliminate the causes of such a situation.
Budget: 3500 UAH Deadline: 1 day
Hello! I will complete your task quickly and efficiently. What is the website built on?
My portfolio: https://freelancehunt.com/ua/freelancer/romas6ka.html#portfolio
Feel free to write, I will start working today. I look forward to collaborating with you!
Budget: 700 UAH Deadline: 7 days
I am engaged in hosting
I will look at a Linux server or regular hosting,
Budget: 5000 UAH Deadline: 2 days
I will find the reason for the growth of inodes — most often it is sessions, logs, cache, or junk files from cron/plugins. I will check the file system, database, temporary directories, set up auto-cleaning, or fix the source of the leak.
What is the website built on — WordPress, Laravel, or another framework?
Budget: 1000 UAH Deadline: 1 day
Good day. I have experience solving such problems. I am ready to analyze the situation and help you.
Budget: 700 UAH Deadline: 1 day
Good day. I have the opportunity to help you. Please feel free to reach out. Thank you.
Budget: 1000 UAH Deadline: 2 days
We can do it. Payment upon verification. I guarantee the quality.
Budget: 1000 UAH Deadline: 1 day
I believe the hosting is heavily compressed, we should switch to another plan. Generally, a common solution is to set up a cleanup script linked to the scheduler. I would do it, it's not my first time.
Budget: 1000 UAH Deadline: 3 days
Good day!
There is an increase in the number of inodes and occupied space on the hosting that cannot be resolved by cleaning. I am ready to deeply analyze the causes of this phenomenon, using my experience with system logs and server configurations, and find an effective solution to the problem.
Write to me, and we will discuss the details.
Budget: 800 UAH Deadline: 1 day
Hello. I manage hosting and VPS. Feel free to contact me, and we can discuss the details.
Budget: 700 UAH Deadline: 1 day
Good day. I can optimize the space on the hosting and find out what is taking up your storage. If you have any questions, you can write to me in private messages.
Budget: 1199 UAH Deadline: 1 day
Hello.
I can perform a hosting diagnosis and find the reason for the increase in inode and occupied space.
I will check:
* logs;
* cron jobs;
* cache/backup;
* temporary files;
* possible cyclic records or unnecessary file generation.
I am ready to connect and look into the problem.
Budget: 4000 UAH Deadline: 2 days
Good day, Oleksandr! Sometimes the inode count increases again after cleaning — this almost always means that some process is continuously generating files and not cleaning up after itself. The most common culprits are: PHP sessions without rotation, logs without auto-cleaning, mail queue (Exim/Postfix), or a WordPress plugin that writes temporary files.
I will start with diagnostics: I will find directories with the highest inode growth using du/find, check the web server logs, MySQL and PHP logs, the mail queue, and active cron jobs. After identifying the source — I will set up log rotation, session cleaning, or fix the problematic plugin/cron, and also add a simple monitoring script for alerts on the next increase.
I have done similar diagnostics on shared hosting and VPS — usually, the source is found within the first hour or two, the rest goes to fixing and preventive measures. Estimated time: 5 hours, $100 (≈4,000 UAH), deadline 1-2 days. Please clarify: do you have shared hosting (cPanel/ISPmanager) or VPS with SSH access?
Budget: 1234 UAH Deadline: 1 day
Good afternoon. What hosting? What is the site built on? Please write in more detail, I will figure it out.
I assume that you have logs or many images stored somewhere.
Price after review.
There is an active production platform with a catalog and automatic updates of external offers and prices. Stack: — Node.js / TypeScript; — PostgreSQL; — existing price refresh service and cron; — separate ready Python module for validation and selection of offers; — staging and production. It is necessary to make targeted improvements to the existing price refresh pipeline without completely rewriting the backend. MANDATORY SCOPE 1. Integration of the Python module — The Python module remains a separate component; — returns a structured result: offers, selected offer, statuses, and risk flags; — Node.js validates the result and performs a write to the database; — provide for error handling and partial/failed runs; — the legacy pipeline is not turned off until QA is completed. 2. Launch refresh by list Add launch: — by one slug/id; — by the provided list of slug/id. Assume CLI or existing service API. A new user interface is not required. 3. Shadow Mode New results must be recorded separately and not affect production until QA. Shadow fields required: — price; — selected offer ID; — direct URL; — offer status; — risk/QA flags; — checkedAt; — engineVersion. 4. Expanding the existing offers table Add: — source; — external_offer_id; — last_seen_at; — last_checked_at; — engine_version; — risk flags or storage in existing JSON; — unique constraint to protect against duplicates. It is not required to create a new parallel offer system if the existing table can be safely expanded. 5. UPSERT, STALE, and DB transaction Replace the current DELETE → CREATE scheme: — UPSERT existing and new offers; — offers missing in the full successful snapshot are translated to STALE; — in case of API error, partial result, or incomplete snapshot, active offers should not become STALE; — updating offers, selected offer metadata, and shadow fields for one model is performed within one DB transaction; — in case of an error, a full rollback is performed. 6. Canonical-safe refresh Price refresh should not change: — brand; — reference; — model; — collection; — name/title; — slug; — descriptions; — images; — SEO fields. Only offer, price, and shadow data are updated. 7. Preserving current cron logic Preserve: — existing cron; — rolling batches; — cooldown; — checking PRICE_REFRESH_MIN_DAYS before calling the external API; — legacy production pipeline until Shadow QA is completed. 8. Audit output One option is sufficient: — shadow columns in the existing admin table; or — CSV export. Minimum data: — model/reference; — production price; — shadow price; — delta; — production/shadow URL; — status; — risk flags; — checkedAt; — engineVersion. A new complex dashboard is not required. 9. Staging and QA — DB migrations; — staging deployment; — smoke test on 5 provided models; — then Shadow Mode on approximately 50 models; — fixing technical errors identified during these runs; — brief documentation of the Python → Node.js contract and rollback procedure. OPTIONALLY ASSESS SEPARATELY Simple technical promotion without a new UI: — promotion of one model by slug; — promotion of a list of slugs; — transferring confirmed shadow values to production; — technical check after rollout. RESULT — Pull Request; — DB migrations; — working integration Python → Node.js; — Shadow Mode; — UPSERT, STALE, and transactional update; — launch by slug/id; — staging deployment; — smoke-test results; — brief documentation; — at least 7 days of bug fixes for the implemented scope after acceptance. IN RESPONSE, INDICATE 1. Fixed price for the mandatory scope. 2. Separate cost for the promotion mechanism. 3. Timeline. 4. Hourly estimate. 5. When you are ready to start. 6. Experience with PostgreSQL transactions, migrations, and ingestion pipelines. 7. What questions need to be clarified before starting. 8. Whether staging, QA, migrations, and bug-fix period are included. Template responses without specific estimates will not be considered. Access to production is not provided at the first stage. Work begins with limited code review and staging.
A centralized server system for collecting and storing data from Planfix, 1C, Meta Ads, and Google Ads is needed, as well as a web dashboard for displaying and analyzing this data. All data, change history, calculations, and aggregated metrics must be stored exclusively in the server database. The dashboard should not store or duplicate business data. It must retrieve the necessary information from the server database via API according to user requests and display it in the form of KPIs, charts, tables, and detailed reports.
We are looking for support for a project based on Yii , we need to make edits and improvements to the database, there is partially a connection with the previous contractor .....................
It is necessary to migrate the database from CRM G-PLUS to MyChatBot Database volume - 26 thousand leads 2 funnels - Call center and Sales department with their own funnels Lead cards (besides name and number) have many different fields Leads also have voice recordings of calls. These also need to be transferred I expect an approximate amount and implementation timeline from the candidate
Create a dashboard for monitoring and analyzing the performance of the company's location network (branches) in Google Business Profile (GBP) through the official Google Business Profile API. Process via a script based on Google Apps Script (link to Google Sheets). Record data in Google Sheets (which serves as a database for Looker Studio). Update: Daily (with an indication of the last update date). Create a Google Cloud service account. The script runs once a day (trigger at 03:00 AM) and sends a request to the GBP API. It retrieves metrics for the previous day for each location (locationId). Records data in a flat format (row = unique combination of Date + Branch ID + Metrics). Key Performance Indicator CardsCard NameGBP MetricDynamic FormatProfile ViewsImpressions (Search + Maps)Percentage %, Sparkline (blue)CallsLocal Services Phone CallsPercentage %, Sparkline (green)Website ClicksWebsite ClicksPercentage %, Sparkline (purple)Direction RequestsDirection RequestsPercentage %, Sparkline (orange)Average RatingAverage Review RatingAbsolute change (e.g., +0.1), Sparkline (yellow)New ReviewsNew Reviews CountPercentage %, Sparkline (turquoise)