Ortus BoxLang Cloud Servers
  • Welcome To The Cloud
  • Intro
    • Overview
    • About this Book
      • Author
    • EULA
  • aws
    • Overview
    • Ubuntu Based Images
      • BoxLang with CommandBox
      • Boxlang MiniServer with Nginx
      • Other Engines
        • Lucee + Nginx
          • Managing your web site
            • Connecting to your server
          • Changelog
        • CommandBox + Nginx
          • Managing your web site
          • Connecting via WinSCP
            • Connecting via VSCode
              • How to customize sites
              • Changelog
    • Windows Based Images
      • BoxLang with CommandBox
      • BoxLang MiniServer with IIS
      • Other Engines
        • Lucee + IIS-Boncode
          • Managing your web site
          • Connect with VSCode
          • Changelog
        • Commandbox + Boncode
        • Contentbox 5
          • Running Contentbox
          • Connect with VSCode
  • microsoft
    • Overview
    • Ubuntu Based Images
      • BoxLang with CommandBox
      • BoxLang Miniserver with Nginx
    • Windows Based Images
      • BoxLang with CommandBox
      • BoxLang Miniserver + IIS
  • googl
    • Coming Soon...
  • Digital Ocean
    • Coming Soon..
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
Export as PDF
  1. aws
  2. Ubuntu Based Images
  3. Other Engines
  4. CommandBox + Nginx

Managing your web site

This page will show you how to mange your site using CommandBox and how to move files back and forth from your your development environment where ever that may be.

PreviousCommandBox + NginxNextConnecting via WinSCP

Last updated 4 years ago

Was this helpful?

Now that you have a site running in the cloud you will want to customize it. Remember that SSH pem file you downloaded. That is going to allow you to go on the server and edit files. If you are on a windows, Mac or Linux platform, here are some tools I strongly suggest that you get locally. The instructions below are for Windows but all of these tools are available for all 3 platforms.

  1. CommandBox. This tool will allow you to make files and remove them locally. If you so decide that you want to edit and add files directly on the EC2 instance this can be done using the default instance of CommandBox on the server.

  2. VSCode the editor of choice, and the reason I say that is because it has so many useful extensions.

  3. WinSCP the default file manager tool for Windows.

If you are using the Windows Package Manager you can download all of these from there.

Here is a script to download them in Powershell. Save the script as anything.ps1. Remember where you saved it. With PowerShell, you must make sure is not Restricted. We suggest using Bypass to bypass the policy to get things installed or AllSigned for quite a bit more security.

  • Run Get-ExecutionPolicy. If it returns Restricted, then run Set-ExecutionPolicy AllSigned or Set-ExecutionPolicy Bypass -Scope Process.

Go to the right corner of the dialog box below and copy this script and save it naming it whatever you like as long as the extension ends as *.ps1

#Install Chocolatey
Set-ExecutionPolicy Bypass -Scope Process -Force; [System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072; iex ((New-Object System.Net.WebClient).DownloadString('https://chocolatey.org/install.ps1'))

#Assign Packages to Install
$Packages = 'commandbox',`
            'vscode',`
            'winscp'

#Install Packages
ForEach ($PackageName in $Packages)
{choco install $PackageName -y}
PS> .\anything.ps1 (enter)

If your scripts successfully installed you should see a new desktop icon for VSCode. If you open a shell ( CMD, Powershell, git bash ) and type box you should see that CommandBox is installed.

https://commandbox.ortusbooks.com/
https://code.visualstudio.com/download
https://winscp.net/eng/index.php
Chocolatey
Get-ExecutionPolicy