Burris Builder Home
After you have successfully built a website, you are provided with management panel for that website. You will be brought here automatically upon successful website creation. In order to return to this page, you may also select the page from your website listing on the homepage.
The Homepage Website List
After building your new website, you will find your website listed on the homepage table. After you have created several websites, an assortment of organizational tools are available. The listing will become paginated after 10 websites. You may sort according to the clickable table headers, and you may filter according to an assortment of website properties.
Selecting a website in the name column
The homepage table is created as a Drupal View. Those of you familiar with Views will find it available for customization, after the Views UI module is turned on. Views is outside the scope of this documentation, however.
The Management Panel contains the assortment of functions available for individual websites created
This panel describe the WebDav file access available for your website. The WebDav provides the advantage of not needing any 3rd party client software as it is supported by every major OS. A WebDav connection may be mounted as a drive your computer, just like any other attached storage device, so you may save directly to your website just as you would to your hard drive from any program. There are secured and standard access, essentially for Mac or Windows devices.
Since WebDav is an HTTP protocol it may be tested in any web browsers. Simply open either address in a URL just like any other website and type the username and password when prompted. If successful you should see file listing and be able to browse the contents of your website. This will be a read-only format.
Windows 8 File Access
Mac File Access
This panel is only visible for Drupal or WordPress websites. It contains the login information. The admin screen may be accessed easily by clicking "Admin Login".
Password is hidden from view by default and you must have the "View Password" permission to view the password. Click "Show password" to reveal it. Each password is encrypted when stored in the database, according to a key stored on the on the Burris Builder drive, and then decrypted for display.
Changing the email, username or password from the Edit tab does not currently change the credentials of the admin user. This is currently on the planned features list.
The credentials and connection info being displayed here are either being used for Drupal or WordPress websites, or may be used if you selected to create a database for a Git or Blank website.
Just other credentials are handled, the database password is hidden from view by default and you must have the "View Password" permission to view the password. Click "Show password" to reveal it. Each password is encrypted when stored in the database, according to a key stored on the on the Burris Builder drive, and then decrypted for display.
Changing the endpoint, database credentials from the Edit tab does not currently change the credentials of the admin user. This is currently on the planned features list.
When Burris Burris creates a website, it creates a username and password which has full access to that database, and only that database. The only permission not given to the user is "Grant". The username may be shortened from the database name, since only 16 characters are supported, the user name will be trimmed at the 16th character.
For convenience, logs may be viewed directly through the management panel. Clicking the first link will present the "tail" of the logs in order to retrieve the most recent entries. This link is also the physical location of the logs on the server.
Additionally, the entire log file may be downloaded by clicking the "Download Error Log" or "Download Access Log" respectively.
The level of logging is determined by level selected for the website. Dev, stage and live websites will progressively reduced amounts of logging. Every website turns off logging to access logging to assets such as images.
This option is only available to Drupal or WordPress websites. It allows you to update the websites in their entirety, or install additional modules or plugins.
In order to run properly, permissions may be adjusted to your website file structure. The permissions default back to "tighten" settings (as explained in the Permissions section on this page) after the update has been run. The permissions are suitable for their respective systems (e.g. the files directory remains writable for Drupal), you may want to run Drush of WPCLI commands yourself if your permission is very specific.
These options simply run Drush or WP-CLI commands for you. To learn more about the Drush or WP-CLI, follow the links below.
Clicking update website will return results from the respective command line interface, indicating if any updates are available. To process, click the "Update" button. That's it. You're done.
Add Module or Theme
On this screen, Drupal supports merely typing in the name of the project. Drush will determine whether the name is a module or theme and load the project. WordPress website require the entire URL, for instance pasting https://wordpress.org/plugins/jetpack/ into the input box will load JetPack onto your website.
These buttons will download the website files in their entirety to your hard drive. If your website has a corresponding database, that will also be available. Click the corresponding button and save the file to your desired location.
This facilitates the creation of a CloudFront Content Distribution network. It will create the distribution required, write corresponding configuration files and create Route 53 entries for you to give you a location to start server distributed assets in roughly 20 minutes; the time it takes to build a distribution.
If you have already created a C, your origin and distribution addresses will be listed here.
AWS does not charge for creating or maintaining a content distribution network or for delivering data from your web server to the points of presence (the distribution servers). AWS does charge for data delivered to customers from the network, according to the price class you choose.
Like every AWS service, you pay only for what you use. For a very high traffic website your costs can vary substantially by delivering proper cache headers, implementing gzipping, and using compression for images or other assets. Burris Builder employs some best practices automatically, for you, but a general understanding of CDN delivery is recommended.
Create a CDN
CDN Domain is the domain from which you will server all of your assets. For instance, once your CND is setup you would server you CSS, JS or image assets from cdn.example.com.
Origin Domain is the address from which your web server delivers assets to the CDN. You will never use this address publicly, it will only be used to adjust Nginx configuration files.
Price Class by default is set to the cheapest option, of US and Europe Only. Choose other pricing classes if you'd like your assets to be delivered with better performance to additional regions.
When you're finished, click "Create CDN". It will take roughly 20 minutes for the CDN to become active. After which, you may begin delivering assets to your CDN.
Login and credential information may be managed here. Username be created, reset or deleted from this panel.
Users created here affect the entire EBS volume. So any website which exists on the "/www" drive, for instance will also have the same username and password
To add a user select which type of user you would like to add, standard (for Windows) or secure (for Mac) and
After a user is created, you may only reset the password, they cannot be displayed.
Volume If you have more than one volume available, you may select which volume you would like this to apply to. The volume the website is located on is selected by default.
This section describes managing the users for WebDav. For login information see the Access section of this document