Cloud Computing

These are my personal cloud computing notes for ASHIS.SITE topics, especially configuring, deploying, and managing open-source software in the cloud.

The official ASHIS.SITE page lists cloud computing and connects it with open-source software deployment and management. I use this page to record cloud planning notes without naming unsupported cloud providers or products.

My cloud computing goals

These are personal notes for my own learning, building, and experiments. They are not written as cloud computing instructions for other people, clients, organizations, or teams.

Cloud computing lets applications, storage, databases, and infrastructure run on managed platforms instead of physical servers. I use these notes to think through reliability, security, cost, and operational simplicity.

I focus on these goals:

Choose services that match the workload and team experience.
Automate deployments so releases are repeatable.
Secure access with least privilege permissions.
Monitor availability, errors, performance, and cost.
Plan backups, recovery, and scaling before traffic grows.

Cloud scope for ASHIS.SITE

Cloud computing on ASHIS.SITE stays connected to practical project operation. My goal is not to describe every cloud concept, but to plan where software runs and how it stays reliable.

Scope area	Planning question
Hosting	Where will the website, app, or open-source software run?
Deployment	How will changes move from local work to a live environment?
Configuration	Which settings, secrets, and environment variables are required?
Management	Who reviews updates, logs, backups, and failures?
Monitoring	How will problems be detected before users report them?
Recovery	How will data and service be restored after a failure?

My workflow

Define the workload

Identify whether the project needs static hosting, server-rendered pages, APIs, background jobs, databases, object storage, or scheduled tasks.
Select the hosting model

Choose a model that fits the workload: static hosting, containers, serverless functions, virtual machines, or managed application hosting.
Configure environments

Separate development, staging, and production environments. Keep secrets out of source code and store them in an environment or secrets manager.
Automate deployment

Use a repeatable deployment process with build steps, tests, environment variables, and rollback instructions.
Add monitoring

Track uptime, error rates, response times, logs, resource usage, and spending. Create alerts for issues that need action.

Deployment planning

I write a deployment plan before running important software in the cloud. The plan should be short enough to follow during a release and detailed enough to repeat later.

Include:

What is being deployed.
Which environment receives the deployment.
Which configuration values are required.
Which checks must pass before release.
How to confirm the deployment worked.
How to roll back if something fails.

Environment planning

Separate environments reduce risk. At minimum, distinguish between local work and production work.

Environment	Purpose
Local	Used for development and early testing.
Staging	Used to test changes before they affect real users.
Production	Used for the live website, app, or deployed software.

Keep production access limited. A mistake in production can affect availability, data, cost, and trust.

Operations documentation

Cloud projects need operations documentation because deployment is only one part of running software.

I document these areas:

Area	What to document
Start and stop	How the service starts, restarts, and shuts down.
Logs	Where to find application and system logs.
Errors	Common failure signs and first checks.
Updates	How dependencies and software versions are reviewed.
Backups	What is backed up and how restoration is tested.
Access	Who can access the environment and why.

Personal cloud planning checklist

Area	Check
Hosting	The hosting model matches the application workload.
Security	Access is limited to the people and systems that need it.
Secrets	API keys, tokens, and passwords are not committed to source code.
Deployment	Releases are automated and can be rolled back.
Backups	Important data has a tested backup and recovery process.
Monitoring	Logs, metrics, alerts, and cost tracking are enabled.

Cloud management checklist

I use this checklist when managing deployed open-source software:

The deployed version is recorded.
Configuration values are documented.
Secrets are stored outside the codebase.
Backups are enabled for important data.
Recovery steps are tested.
Logs are available for troubleshooting.
Updates are reviewed before production release.
Access is limited to required users or systems.
Monitoring covers uptime and errors.
Cost changes are reviewed regularly.

Optional: Scaling strategy

Plan scaling based on the bottleneck. Static sites often need better caching, APIs may need horizontal scaling, databases may need indexing or replicas, and background jobs may need queues.

Troubleshooting

Deployments fail unexpectedly

Check build logs, environment variables, dependency versions, and required permissions. Compare the failing environment with the last successful deployment.

Costs increase quickly

Review traffic, storage, logs, database usage, idle resources, and autoscaling settings. Add budgets or alerts so cost changes are visible early.

Users see intermittent errors

Check service health, application logs, rate limits, database connections, and recent deployments. Roll back if the issue started after a release.