Where to Start

The Microscript catalog contains ready-made PHP scripts for different business models: trading platforms, classifieds, shops, marketplaces, portals, and review services. This manual does not replace the product page on the main site and is not a contract. It helps you choose the right direction, understand where the installation belongs, and make the first steps without chaotic expectations.

If you are at the stage of "I have an idea, but I do not know which script I need", this article is for you. If you have already bought a license, still review the choice once more: people sometimes install a classifieds board when they actually need a marketplace, and the other way around.

What each product type covers

• Binary Options Platform and Forex mean a trading terminal, accounts, quotes, and a user cabinet. They are often used in a white label model.
• Classifieds board means classified ads: listing, city, photos, contacts. See classifieds.
• Online shop means catalog, cart, and checkout. See shop.
• Freelance marketplace means jobs, bids, and deal statuses. See marketplace.
• Game portal means a release catalog and game pages. See portal.
• Review service means company profiles, TrustScore, and a widget. See reviews.
• Quotes service and quotes API mean data for charts and external terminals.
• Turnkey website or landing page means a custom presentation site, not a boxed business model. See turnkey.

Rule of thumb: start with the money model and entities, then move to design. A beautiful theme will not turn a classifieds board into Forex.

How to choose in 15 minutes

1. What does the user do on the home page: publish a listing, add to cart, open a deal, download a page, write a review, or trade?
2. Does the product include a cabinet with balances or accounts?
3. Who pays you: the buyer, advertiser, deal commission, subscription, or broker spread?
4. Do you need a unique presentation site without this logic? Then you need turnkey work, not a script.

If your answers are vague, do not buy the largest package "just in case". Contact support or narrow the niche on paper.

Work order after the choice

1. Prepare the environment: PHP 8 and MySQL. Locally use MicroServer; in production use a VDS or hosting with the required extensions.
2. Install the chosen script and complete the initial admin setup.
3. Connect the domain, HTTPS, and mail.
4. Connect payments if the product uses them: test mode first, production later.
5. Check public pages and the user cabinet in a clean browser.
6. Add minimum content before advertising: categories, demo products, demo jobs, or listings.
7. Configure backups.

Installation is covered in the install manual in this catalog. Do not skip mail: without messages, cabinets look silent and you may think the script is broken.

Local and production environments

A local stand is for breaking and configuring without embarrassment. Production is for customers. Do not test payment keys only in production. Do not use the same admin passwords on staging and production. Migration has its own checklist: code, database, uploads, configs, cron.

MicroServer is convenient on Windows for .loc hosts. On a VDS, check write permissions, cron, firewall, and SSL. The manual catalog has separate articles on hosting, SSL, chmod, and 500 errors; use them when you hit the issue, not weeks later.

What not to do at the start

Do not promise customers features from another product. Do not open registration without moderation where spam destroys the model: reviews, marketplaces, classifieds. Do not repaint a white label before the basic account scenario works. Do not confuse a landing page with a corporate site, or a shop with a classifieds board.

Do not start by rewriting the core "just a little". First launch the stock product, understand it, and then choose customization points. Otherwise updates and support become a quest.

How to use this manual

Sections and category filters are on the left, cards contain excerpts, and each article builds a table of contents from H2 headings. New texts are added as files in articles; see how to add an article. Internal links point to other manuals on this domain. Product pages on the main Microscript site are for choosing a license and package contents.

Minimum launch team

Even a small product needs roles: who sets up the server, who configures the product, who writes texts and categories, and who answers support during the first week. One person may cover several roles, but the task list must be explicit.

Budget for more than the license: VDS, domain, SSL, mail, payment fees, advertising, and a reserve. A script without traffic and without mail does not earn.

Legal wrapper: offer terms, data policy, and risks for trading platforms. This is not just footer text; it is what you rely on in a dispute. Consult a specialist in your jurisdiction; this manual is not legal advice.

After the first production day, run a retrospective: what broke, which tickets appeared, where the admin panel was slow. Three improvements for next week are more useful than a beautiful yearly roadmap.

Map of the next manuals

After choosing the product, read the narrow manual for that cluster: for freelance, the marketplace and escrow; for games, the portal and download page; for reviews, TrustScore and moderation; for trading, white label and cabinet. The technical track is shared: install, PHP/MySQL, hosting, SSL, backups. Do not try to read all manuals in one day; follow your vertical.

If you are stuck on a 500 error or database issue, the catalog has dedicated breakdowns. Send license support facts: product, environment, and what you have checked. That is faster than "nothing works" without logs.

A local MicroServer experiment reduces the risk of breaking production. Break staging and rebuild it. Break production without a backup and the conversation is different.

Readiness for the first production week

Checklist: nightly backup, access to logs, test user, support status/contact page, a real admin password, and certificate monitoring. If the product handles money, add a payment reconciliation checklist. The first week exposes real gaps better than any specification, so schedule duty time, not only a launch moment.