EN
TH
EN
TH
Custom Development
Amity Tech Documentation

Find the right guide before you change a live system.

Start by product or by task. Each path keeps requirements, release checks, backups, verification, and the right support channel close at hand.

Browse by task Choose a product
Product paths

Start with the software in front of you.

Product pages carry release-specific requirements and files. This hub covers shared operating practices and routes you to the authoritative detail.

Scoped to each engagement
ASP.NET Core & integrations

Project documentation

Architecture notes, runbooks, deployment, and handover are produced for the actual system instead of presented as generic instructions.

Browse by task

Go directly to the job you need to complete.

The six core guides form one safe operating sequence. You can enter at any point without losing the checks around it.

01

Getting started

Choose a product, confirm scope, requirements, and the official release source.

02

Installation

Prepare staging, separate application files from data, and verify the first run.

03

Upgrade

Read release changes, protect the recovery point, and define rollback criteria.

04

Backup & restore

Protect database, configuration, and uploads—and rehearse recovery.

05

Troubleshooting

Capture useful evidence, isolate the failing layer, and avoid risky guesses.

06

Security & privacy

Review access, secrets, retention, backups, and personal-data handling.

Production-safe workflow

Four checks before every meaningful change.

Documentation supports a decision; it does not replace a recovery plan or validation against your own environment.

  1. 01

    Match the release

    Confirm product, version, compatibility, checksum, and release notes.

  2. 02

    Protect the recovery point

    Back up data, configuration, uploads, and the installed package.

  3. 03

    Rehearse in staging

    Use the same package and reproduce the workflows that matter.

  4. 04

    Verify or roll back

    Check migrations, login, email, files, integrations, and recovery signals.

How to read these docs

Know which source is authoritative.

Shared guidance stays useful across products, while release-specific facts remain attached to the software they describe.

01

Release-specific truth

When two documents differ, use the information shipped with or attached to the exact release you are installing.

  • Product page: current release, requirements, checksum, and source
  • Package README: exact installation and configuration for that build
  • Changelog or development tab: changes, limitations, and upgrade notes
02

Documentation vs support

Public documentation explains the supported path. A private request is the right place for account, installation, or environment-specific problems.

  • Never paste passwords, API keys, licence secrets, or personal data
  • Include product, version, environment, exact error, and reproduction steps
  • Custom changes and implementation work are scoped separately
Still blocked?

Move from reading to a trackable support path.

Open a private product-support request for your environment, or search public discussions for reusable answers.

Open private support request Browse support community
Powered by Amity Tech CMS