AccuWeb.Cloud Environment Deployment Guide

The AccuWeb.Cloud platform offers different ways to automatically set up your applications. You can pick the one that fits your needs best. There are many deployment options available, so you can make your deployment strategy just the way you want it.

Dashboard: This is an easy way to deploy your apps using archived files. Whether these files are on your computer or a specific web address, the Dashboard makes it simple to start deployments.

VCS (Version Control System): You can also deploy your apps directly from your VCS repository. This includes popular platforms like Git, SVN, and Bitbucket.

Hub Registry: If you work with containerized apps, you can use the Hub Registry option. It lets you create a customized container for your app using a Docker image from your public or private storage. This is useful for making your apps scalable, portable, and efficient, especially in container environments.

If you want to know more about the last two options, you can click on the right links.

In this guide, we’ll show you how to put your app on the platform using a box (archive) or from a special storage place (VCS repository). You can do this from the Deployment Manager or by hovering over the Deployments thing and clicking the right button.

The first two pictures (Local file and URL) are for putting your app in a box (archive). The last one (Git / SVN) is for putting your app from a special storage place (VCS repository). Just pick the one you need and click it to set it up.

1. Archive Deployment Configurations

Setting up your archive deployment is easy. It only takes a few seconds to get started. You just need to do two things:

• Give it the archive file you want to deploy.
• Tell it where you want to put your application.

You can also make things work exactly the way you want by changing some extra settings.

Here’s what you can do in the deployment setup:

• Environment: This is where you pick where your application should go. When you’re using the application server, it’s also chosen automatically.
• Path: You can choose a custom context if you want. But remember, some programming languages like Python and Node.js only have one option here.
• Hooks: You can use scripts before or after the deployment process if you need to.
• Deploy Strategy: If you’re putting your app on multiple servers, you can choose how to do it. You can either do it all at once, which is faster but causes a little downtime. Or you can do it one server at a time with delays in between to keep your app up.
• Enable Zero-Downtime Deployment (for PHP servers only): If you’re using PHP servers, you can make sure your app doesn’t have any downtime during deployment by checking this box.

Just click “Deploy” to start the process. It’s that simple!

2. Git / SVN Deployment Configurations

Setting up your Git or SVN deployment is very easy and quick. You can get started in just a few seconds by doing two main things:

• Choose the Git or SVN project you want from the Deployment Manager.
• Tell it where you want your application to go.

You can also make your deployment work just the way you want by changing some extra settings.

Here are the options you can adjust:

• Repository: This is where you pick the Git or SVN project from the Deployment Manager. You can also add a new one if needed.
• Branch: You can choose which branch of your project to use. Usually, it’s set to “master” by default.
• Environment: This is where you pick where your application should go. If you’re using an application server, it’s selected automatically.
• Path: You can choose where your app should be placed. But keep in mind, for some programming languages like Python and Node.js, there’s only one option.
• Build (for Java application deployments): If you’re deploying a Java app, you can choose how to build it. You can use an existing Maven build node or add a new one to your environment. You can also pick the repository’s working directory if needed.
• Hooks: You can use scripts before or after the deployment process if you need to.
• Deploy Strategy: If you’re deploying on multiple servers, you can choose how to do it. You can either do it all at once, which is faster but causes a little downtime. Or you can do it one server at a time with delays in between to keep your app up.
• Check and Auto-deploy Updates: You can set it to check your code regularly for changes in your repository. If it finds any changes, it will automatically deploy your project.
• Auto-resolve Conflicts: This helps avoid conflicts when different people make changes to the same file. It updates the file with the repository’s version, so any changes you make are discarded.
• Enable Zero-Downtime Deployment (for PHP servers only): If you’re using PHP servers, you can make sure your app doesn’t have any downtime during deployment by checking this box.

Just click “Deploy” to start the process. In a few minutes, your application will be deployed successfully. You can access it through the “Open in Browser” button, check the logs, or manage it using the file manager or SSH access.

3. Editing Git / SVN Projects

If you want to change something in a VCS project you’ve already set up, just click the “Edit” button for that deployment.

When you’re in the editing window, you can change the same things we talked about earlier, like the branch or the hooks. You can also turn on automatic updates if you want.

4. One important thing to remember

If you change the login details for the project’s repository, you’ll need to give the new details to the platform so it can keep working with your project.

First, go to the Deployment Manager and update your authentication for the repository there.

After that, you’ll need to edit all the projects you’ve set up from that repository. The platform will ask if you want to use the new login details. Just say “Yes” to apply them to your project.

Conclusion

To sum it up, AccuWeb.Cloud gives you many ways to put your application online. You can use the simple Dashboard for archives or URLs, connect your code using Git, SVN, or Bitbucket, put your app in a container with Hub Registry, or use your favorite tools like Eclipse, IntelliJ IDEA, Netbeans, Maven, or Apache Ant with Plugins. You can choose the way that suits you best.