• Studio

  • Please watch the video by clicking the icon on the right.

    There's no specific limitation on the number of sites you can add to the studio.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    We can choose to take over the hosting.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    ​You can use .CO.NZ domain with our hosting. To register a CO.NZ domain you have to use a (local) domain registrar (we don't offer registrations of .CO.NZ domains ourselves because of the price. After you registered or transferred the .CO.NZ domain, you need to configure the DNS entries of the domain to point to our servers. For the Asian Pacific server; add the following 2 records (replace example.org with your domain); A record: studio.example.org value: 52.64.97.173 A record: *.studio.example.org value: 52.64.97.173 NOTE: ensure you do NOT have any AAAA (ipv6) records configured in the DNS records Once you have updated the DNS records on the DNS server, send an e-mail to support@nexusthemes.com and instruct us to update the hostname of your studio (provide us with the hostname you want to use, studio.example.org in this example). The recommended value for the TTL to use for these records is 3600 (any other value would be ok too, although in general the lower the value, the better). The TTL value defined the number of seconds a web site visitor's computer is allowed to cache the lookup entry. So 3600 stands for 1 hour. Should the studio ever switch to a different IP, till means in the worst case this will take 1 hour to be processed.

    Please watch the video by clicking the icon on the right.

    We don't have a mail server. We do have a mail redirect service. That means you can use domain-specific email addresses to send and receive emails.

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    Moving a website away from the hosting of Nexus Themes to some place else is explained in the following videos; Step 1) Download the backups of the site from the hosting environment https://www.youtube.com/watch?v=eGw5JqCD4s8 Step 2) Override the hostname https://www.youtube.com/watch?v=mDxLRVLql24 Step 3) Installing WordPress https://www.youtube.com/watch?v=4ovXmRQAYwc Step 4) Importing the DB dump https://www.youtube.com/watch?v=S70MEURtEjo Step 5) Setting up WordPress https://www.youtube.com/watch?v=QiMWMFuIq2Y Step 6) Optionally upgrade the WP DB https://www.youtube.com/watch?v=N7ZBzbZaZjk Step 7) Installing and activating the theme https://www.youtube.com/watch?v=gtf_6AC0ASw Step 8) Installing and activating plugins https://www.youtube.com/watch?v=UHxZU-1MV1w Step 9) Uploading the contents of your site through FTP https://www.youtube.com/watch?v=ePA5bT_Qh58 Step 10) Making yourself an administrator using MySQL If transferring the domain requires a transferkey, then you can request the eppcode through the portal. Steps to get the transfey key and to enable or disable the transfer lock are as follows: Step 1; Login to the portal; https://my.nexusthemes.com Step 2; Select the order connected to the domain Step 3; Click on "Manage domain" Step 4; Follow up the steps there

    We do active monitoring on the uptime of our servers, see here; https://status.nexusthemes.com/. The moment we receive a notification of something not ok, we do our best to resolve the issue as fast as we can.

    Plugins are installed on a per-site basis. We don't update these plugins ourselves because we don't know what they do or how impacting those plugins might effect the site(s). Updating these plugins can be done by either disabling the plugins and removing them from the plugins activator and re-installing and enabling them (for wordpress.org plugins), or in case we made you a WP administrator, you can update the plugins yourself by using the dashboard of the sites. Note that we discourage people to use functionality of plugins of third parties because of the risk of the plugins breaking or conflicting or becoming incompatible.

    We roll out releases when we think thats practical or needed. There's no upfront schedule on when the releases happen, and only we roll them out (meaning you don't do it yourself).

    Please watch the video by clicking the icon on the right.

    The hosted solution we provide through the studio is to support individual websites of small businesses using the features that our themes provide. There are certain features that we don't want our studios to be used for. For example ecommerce solutions, or building community sites (like buddypress/bbpress do). Should you like to offer those, we will be able to provide you with a backup of your current site such that you can transfer to site to a hosting provider that does allow that.

    Please watch the video by clicking the icon on the right.

    After you finish building the website its time to publish it to the outside world. Publishing is done using the following steps;

    Go to the backend of the studio
    In the admin menu select "Sites"
    Hover over the row representing the site you want to publish
    Click on the Publish link
    Select the Client who will become the legal owner of the site (you can add a new client here if you haven't done so yet)
    Select the Domain name you want to use (it could be a new domainname, or an existing one; if its an existing one you can choose whether you want to transfer it to our domain registrar, or if you want to keep it registrered elsewhere)
    Confirm the information at the overview

    We've created the following video which explains these steps in full detail; please note its a 2 step process; first you register the client and domain, and in the second step you publish the site.

    Step 1 - registering the client and domain

    https://www.youtube.com/watch?v=YOI4FeTIGIE

    Step 2 - publishing the site (after you registered the client and domain)

    https://www.youtube.com/watch?v=ykmlvZ7PqDw&feature=youtu.be

    Please watch the video by clicking the icon on the right.

    Our hosting/studio does not support redirection of .php files, you can only redirect pages without an extension (/source => /to, not /source.php => /to). The way the webserver is setup in our specific infra causes it to behave the way it does for php files. Based upon a impact/benefit/risk analysis we've concluded for now we will not be changing our infra. You have to do an analysis yourself on whether or not the redirect of the php are vital for your website. Should it be vital to have .php redirects then for now this unfortunately would imply the site would have to be hosted outside our infra.

    To RENAME an installed site, first go to the list of installed websites in the Studio by clicking on the Sites link in the left sidebar.

    Find the site you wish to rename. When you hover over it you'll see a number of links, click on Map Domain. On the Map Domain page, find the Domain line which contains the URL of the theme. You'll notice that it contains a randomly-generated 'name' at the start of the URL (in front of the FIRST DOT).

    *** BE VERY CAREFUL as you proceed with the renaming! ***

    >>> ONLY the part in front of the FIRST DOT should be changed. <<<

    Replace the randomly-generated name ONLY with something more meaningful and click Update.

    Here's an example for further clarification...

    RANDOMLY-GENERATED URL: hgwhruak.studio.ibefound.nz
    RENAMED URL: companyname.studio.ibefound.nz

    * by using 2FA on the core AWS login (the root access of all VPS-es) of our system administrator root account of Amazon

    * by having a root access document shared with both Johan and Gert-Jan

    * by having a policy in place that logs all incidents on the VPSes

    * by default we don't allow people to get FTP access; only in very rare cases we provide FTP access, only for users who have a large number of sites in their studio.

    * our entire infrastructure consists of multiple VPS-es that have an automated DevOps environment to deploy and sync its vital components that combined form the studio. Those components are stored in a so called "immutable" way; each version of the component is stored on Amazon S3, and each mutatation of the component is stored as a seperate version (once a new release of a component is made, its always stored as a new version; we don't allow changing existing releases). The infrastructure has a system in place to verify the consistency of that component throughout our VPSes; should unexpected differences be identified we can re-sync those components through a system that pulls the versions from S3.

    * through enabling single sign-on; probably you only know one password, which is the password of your studio; you probably won't even know the passwords of the accounts you have in the websites of your clients. The passwords of the sites in the studios are very complex when we created them. This limits the chances of accounts getting hacked. We allow people to use a 2 factor authentication to further restrict access to the site;

    * even if your account would be hacked, we limit the risks since we limit the control to users who own and manage sites; by default only "we" are in the administrator role; studio owners and users in sites in the studio are limited to the "studio admin" role. This "studio admin" role they can't install any plugins (except for pre-accepted ones through the plugin activator section of the backend that we control). Only studio owners who have a significant amount of sites in their studio sometimes become administrator role too, in exceptional cases.

    * we don't allow people to install just any plugin; if people request plugins to be installed outside the ones we white list, we manually review those by checking what the plugins do. If we think the plugins would do harm we don't allow the plugin to be installed.

    * we protect the site by creating periodic backups of each individual site, and by keeping those backups on Amazon S3. We don't have formal policies on how long these backups are kept, but while writing this content its 1 yr (meaning we can go back each day for the last 365 days of an individual site).

    * we also protect the sites by allowing studio owners (as well as optionally end-users) to create backups at any moment in time, and by allowing them to download these backups to their own computers.

    * we protect the sites by creating periodic snapshots of each VPS. We don't have formal policies on how long these snapshots are kept, but while writing this content we keep daily snapshots of each VPS of the last 30 days, and monthly snapshots ever since we started our business.

    * we protect the sites to enable HTTPS on all sites for free

    Please watch the video by clicking the icon on the right.

    We roll out releases when we think thats practical or needed. There's no upfront schedule on when the releases happen, and only we roll them out (meaning you don't do it yourself).

    Please watch the video by clicking the icon on the right.

    Please watch the video by clicking the icon on the right.

    Each WordPress website (this is part of the WordPress core themselves) polls the server of Automattic automatically to check for new minor versions. Once it finds those, it will automatically download and install that minor release over the existing one. We do not update the sites from one major release to a more recent major release unless we believe that would add values to our users. If for whatever reason it would be necessary to update also the major release we will ensure that will happen.

    Please watch the video by clicking the icon on the right.

  • The following questions concern functions exclusively available for clients having chosen to host their website with Nexus.