When starting a DoOO project, your institution may already have existing sites hosted elsewhere that you want to migrate to Domain of One’s Own. (I recommend reading through the Migrations & Transfers category if you need additional assistance with migration workflows.) Maybe your school has existing WordPress sites with custom themes and plugins, and perhaps you’re working with a developer to move them over to DoOO. The following guide will work for any administrator as well, but in the event that you want to hand out only partial access to the person doing the work, keep reading:
1) Developer is given the user’s cPanel credentials
2) Developer logs in directly to user’s cPanel account at https://cpanel.yourDoOOproject.edu
3) Files are uploaded and the site is set up (via FTP or cPanel)
4) “Import” the site files into Installatron viewer. (We have a guide on this here.)
1) Individual cPanel credentials for a user can be found in WHMCS > Client Profile > Product/Services tab:
2) Developer logs in at https://cpanel.yourDoOOproject.edu:
3) Developer uploads files in cPanel (left) or SFTP (right):
One of the many cool things I took away from visiting Coventry last week was how they are re-working their support documentation to be more conceptual and visual. A teaching aide that leads you to a particular issue, rather than just a list of how-to articles. It is still a work-in-progress, but Charlie Legge has been doing some awesome work on this project. In particular, I love the choice of metaphor, namely comparing one’s own domain at Coventry to a house. Brilliant, right?!
This animated visual model of explaining what hosting is and why it matters is pretty awesome. I got a lot of guff about this metaphor back in the day, but I think history is on my side, and it is all but clear that I was right, at least metaphorically Rent, lease, own, or squat, your online data still needs to live somewhere. Thank you, Charlie, vindicare regnum, indeed!
As my first official Account Manager duty, I’ve been sending out the first of many check-in emails to our Domain of One’s Own schools. I feel that it’s important for institutions to hear from Reclaim Hosting more than the occasional support ticket response or invoice reminder email. These check-in emails are separated primarily into two sections: What’s New and Account Analytics.
The What’s New section (which I’ve copied below) will essentially be a newsletter for our DoOO Liaisons to stay up to date on the latest Reclaim Hosting happenings. I’ll be sharing new documentation articles that are produced, new software updates/releases, upcoming events, and internal changes. The Analytics section will look a little different based on each institution, but the general format will include: number of cPanel accounts, number of installs within Installatron, total disk usage on the server, and top 5 high-bandwidth sites. As a side note- I’ve really enjoyed looking at these URLs! This isn’t a feature I check often, but I’m excited to have a reason to continually go back and look at these. It’s been keeping me somewhat in tune with individual projects at schools and I love that.
From there I’ll include suggestions for how a given DoOO school can be using their environment more efficiently. This may mean recommending that they delete Installatron backups, set user quota limits, or add more block storage to their server. Lastly, I’m using this email as a chance to confirm our contact information for Domain of One’s Own team members. We always want to make sure that emails and notifications are going to to the right people, so its good to check on this every now and then!
The goal here is to send this email out at the end of every Fall and Spring semester so folks will be able to track their growth over time. I’ll be keeping track of the data in an excel sheet that I’m sending to institutions so I can reference it in future correspondence.
Forcing HTTPS.Starting in July, Google Chrome will begin to display more prevalent warnings for sites not running on https. View Reclaim Hosting’s response here.
Node.js. As of June 15, it is now possible to run to build and run Node.JS applications at Reclaim Hosting. Read more about this here. As a small caveat, CloudLinux, which is required to run Node.js, is not currently on all servers. If this is something that you’re interested in running, please contact Reclaim Hosting support.
Digital Ocean Customer Story. Digital Ocean recently published a case study on Reclaim Hosting- feel free to give it a read.
As of Late. If you’re interested in reading more about what Reclaim Hosting has been up to recently, you can read Jim Groom’s blog post, Catching up with Reclaim Hosting.
Upcoming Event. Reclaim Hosting will be hosting another Workshop of One’s Own for Domain of One’s Own Administrators this Fall on November 1-2. Seating is limited. More information & registration details can be found here.
We recently migrated UNLV’s faculty websites to a Domain of One’s Own environment. I learned a lot during that migration which in turn helped motivate me to finally clean up the bavatuesdays multi-network site I’ve been putting off for over a year. Well, dabbling a bit every morning last week and yesterday, that is officially done. All sites on the bavatuesdays domain have been migrated and archived—I can take a short break before going after the jimgroom.net network.
In the mean time I have been working on a talk for OER18 wherein Tim and I will be talking about hosting beyond the LAMP environment. Applications that run in other server environments that require Node.js, Ruby, etc. would be nice to offer, but integrating them into cPanel is not necessarily easy. I played with hosting Jekyl from a Reclaim account, but that does require a bit more command line work—which is often a non-starter. But alternatives to cPanel such as Cloudron that allow you to spin up containers that seamlessly manage the application’s server requirements, so all you are doing is choosing a domain to run it on. But we have also been playing with integrating SPLOTs more seamlessly into Reclaim’s offering, so there are several options, rather than any one way forward. Not to mention, cPanel and CLoudLinux are both working to make it easier to run Node.js and Ruby apps in their environment, so it may not necessarily be beyond LAMP at all—but rather within or alongside.
All of this brings me back to UNLV’s Faculty Sites, which have really paired down cPanel to the absolute minimum: WordPress, the file manager, and backups. That’s it. Minimalist, faculty can choose between WordPress or a DIY old school HTML site using the file manager to upload files (or FTP). It does kind of beg the question that I hear all too often about it being overwhelming, or there is too much to learn. No, it’s pretty much your own instance of WordPress, and those little files known as HTML (and a few links) that made the web possible. So, the future is as much within a LAMP environment, as it is beyond LAMP.
Over the last couple of weeks, I’ve made it my mission to build on, add to, and update documentation articles at Reclaim Hosting. This was inspired after our last Workshop of One’s Own event when attendees asked what other schools had done to tweak and add to their DoOO projects. How were schools changing their homepage? How were they handling community support? How were they handling graduating students and their data?
I created a new category on the Workshop of One’s Own Documentation called Customizing your DoOO. This topic is still very much a work in progress, but my goal is to make this a full list of everything that can be safely done or added to a DoOO instance without fear of “breaking the system”. It will include everything from different pages and elements that we can add to a DoOO system, to editing a Domain of One’s Own WordPress theme.
One of the most common “extras” that DoOO schools ask for is the Templated Community Documentation. These are articles written specifically for the students and faculty using Domain of One’s Own. They were written originally by the OU Create team, and were later shared and expanded at other schools. So when new schools start a DoOO Pilot and ask for this documentation, we would copy from one of these existing schools to the new school. This was hardly a bad system, but it’s always bothered me a little bit that we were handing off documentation with another school’s logo on it. It just doesn’t scream “here’s your fresh copy”.
And since every DoOO Project looks a little different, the documentation will look a little different as well. For instance, we have some schools that buy top-level domains for all users and give them access to everything that the default cPanel provides. By contrast, other Domain of One’s Own schools only support WordPress, and have stripped the cPanel down to the very basics. So what may be true for one school may not be true for another. In addition, Reclaim underwent a pricing change a couple of years ago for shared hosting plans & top-level domains to accommodate for ID Protect. What’s more, when software upgrades take place, screenshots need to be updated. And plugins that were relevant 2-3 years ago may now be abandoned by their developers.
I mention all of the above to show that there are clearly a ton of outliers that can lead to a miscommunication and/or change in documentation. So it was time that Reclaim Hosting took ownership of the existing documentation to create a centralized hub of always correct, always up-to-date information. That way any school writing their own docs can always look back at this resource and pull articles that are relevant to their specific projects.
For instance, the team at emerson.build wrote a great article on getting up and running with the Neatline plugin in an Omeka instance. We get questions about this plugin all the time at Reclaim Hosting, so I’m thrilled for finding it! But it also helped reiterate this very real theme surrounding documentation: we need to do more sharing as a Domain of One’s Own community, and Reclaim Hosting needs to help facilitate that. I’m sure there are plenty of schools that would benefit from that Neatline article as I have, so now they can find that article, along with a compiled list of others on State University’s new documentation site: stateu.org/docs
Which brings me to my next point: If you’ve written documentation for your DoOO community, you may receive an email from me in the next couple of weeks asking for permission to add your article to the main hub. You’ve been warned. :) Alternatively, if you’ve written articles that you think would be a good addition to this main list, please contact me!
How is it already the end of November..? I wanted to set aside time this morning to write about my experience at Colgate University a few weeks back before I turn around and it’s suddenly 2018! After the Reclaim trip to NYC, Jim and I traveled to Hamilton, NY for a two-day training session with members of the Learning and Applied Innovation Team and IT Department. But before getting into the content summary– you can’t talk about Colgate without first mentioning the campus. There’s a reason it makes the list of most beautiful college campuses in the states; it really is stunning. My photos throughout this post will hardly do it justice, but I’m including them anyway. 🙂
On day one, Jim and I met early with folks over coffee & bagels. Jim then began the first block by speaking on how DoOO came to be and how it has transformed over the last few years. I’ve heard this talk a handful of times now, so I was able to see past the initial content and focus on how I would approach a similar talk with my own twist. I’ve been shadowing Jim over the last year or so with the idea that I’ll eventually be able to give these talks & trainings on my own, so it felt good to find the headspace to think through some of that.
Next, Jim and I moved into an overview of the Domain of One’s Own platform, bringing everyone up to speed on how WHM, WHMCS, and WordPress work together. Jim gave an introduction to the system, separating out the ‘need to know’ items from the ‘you’ll never really use this’ functions. From there I gave a more detailed outline of WHMCS & WHM and began to walk through the platforms in depth before lunch. We picked up where we left off after grabbing a bite to eat with more hands-on practice in WHM/WHMCS. Similar to one of my sessions during Workshop of One’s Own, we worked through common support troubleshooting fixes, user FAQ’s, and approaching support tickets. We also talked through setting up site syndication, domain transfers and even touched briefly on SPLOTs. And just like that, day one had come and gone.
We spent the bulk of day two feeling out the needs and curiosities of those in the room, focusing heavily that morning on relevant ways to use WordPress, Omeka, Scalar & Drupal. It was cool to watch the team brainstorm and think through ways that their community could take advantage of these tools. I love using slavery.georgetown.edu as an example of an integrated domain for this sort of discussion. Georgetown takes a controversial topic and faces it head-on using WordPress for the main domain and Omeka for the archive. They also embed a historical timeline using Timeline JS, so that’s always a great piece to show as well. We also used Keys to Directing as a great Scalar example, Making Modern America for an Omeka Archival site, and Andréa Levi Smith’s course website for showing how DoOO can be used in the classroom.
Andréa’s site was a great segway into where we spent the majority of our time that afternoon: SPLOTs! Her site was built off a template created by Alan Levine called SPLOTPoint. I wrote more about the excitement of the Colgate Team + SPLOTs here, but it was fun to feed off their ideas and play around with these templates in real time. And as Jim discusses here, we found that one of our most valuable moments of the workshop was narrating our thought process of familiarizing ourselves with these templates on the spot. I had never worked directly with the templates that Alan had created, so I was the perfect guinea pig. 🙂
I installed the SPLOTPoint template on the big screen (on this example domain) while everyone followed along on their own computers. After tweaking settings and customizing that for a few minutes, we moved onto another SPLOT created by Alan called Big Picture Calling Card (on this example domain). I was asked to narrate my thought process for finding settings/making customizations on the theme & template which led to an hour-long discussion on the future and potential of Domains at Colgate.
This trip was valuable to me personally for many reasons. I felt more confident during the technical training portions of the workshop, compared to scenarios where I’ve shadowed Jim in the past. I also felt capable of carrying my own weight and truly tag-teaming the workshop with Jim, as opposed to interjecting every now and again. Jim also offered his critiques, strategies, and advice for talking at great lengths about Domain of One’s Own (a skill he, no doubt, naturally found) so that was immensely helpful as well. And lastly, I discovered a passion for SPLOTs. I was able to see the true potential of installatron templates during the discussions over those two days, and am very much looking forward to their future in Domain of One’s Own and beyond.
Clip from my session on DNS during day one of Reclaim’s Administrator Workshop. During the 45-min talk, we covered DNS basics, types of DNS records and how to edit them, handy DNS tools & strategies, and frequently asked questions.
If you missed the workshop clip on Supporting DoOO, you can find that here.
Documentation guides that I wrote for this talk are linked below:
During a recent trip to Colgate University (another post on that coming soon), Jim and I had a chance to meet with folks on the ground floor and discuss their visions for Domain of One’s Own at their campus. By the afternoon of Day 2, we were focusing pretty heavily on SPLOTs, a concept developed largely by Alan Levine and Brian Lamb. (He talks about them in depth here.) Though this is hardly a new topic of discussion, its brand new for this little web space so I’ll go ahead and explain: A SPLOT, or Smallest Possible Learning Online Tool, is essentially a template that can be added to a fresh WordPress installation. Think of it like importing demo content with a new WP theme, but it’s done automatically when you install WordPress. So for folks that have never used WordPress before, splots are a helpful starting point. They allow users to see the potential of their WordPress site before even beginning.
Here are a few examples of splots that Alan created, taken from our Demo server, StateU.org:
^Each splot is actually an individual install of WordPress aimed towards different uses: portfolios, course sites, class collaborations, archives of writing, etc. He configured each WordPress install with different sets of themes, plugins, images & dummy text, setting customizations, and pages & posts. Once complete, we were able to ‘save’ the install as a template that other users can see at the point of install. Below is a screenshot of a WordPress installation page where the user could install a number of templates or continue with a clean WordPress dash: Continue reading “Sharing SPLOTs Between Servers”
Clip from my session, Supporting Domain of One’s Own, during day one of Reclaim’s Administrator Workshop. During the 45-min talk, we cover strategies for approaching support tickets, user FAQ’s, and common errors.
Now I realize you can’t really see the screen in this video– oops. Hoping we’ll be able to fix that for next time! Still wanted to share this clip as I think it does provide useful information & discussion for DoOO admins.
Documentation guides written for this portion of the workshop are linked below:
Workshop of One’s Own, Reclaim Hosting’s first administrator-focused intensive workshop, has come and gone. And I don’t use the word “intensive” lightly here- it was a dense two days, packed with information that would make even the most qualified admin exhausted, but was amazingly helpful nonetheless.
For this workshop, the Reclaim team really wanted to focus on creating an initial knowledge base of documentation that speaks directly to the Domain of One’s Own administrator. While the DoOO Community Forums can be helpful for certain categories, and there’s a template of DoOO support docs floating around for the community, we felt that there really wasn’t a source for administrators. We realize bringing Domain of One’s Own to a school can feel like a massive undertaking in itself, so if we can help even just a little bit with the onboarding process for new admins, then we’ll consider that a win!
So that was the mindset going in: a workshop for folks that would land somewhere between the Reclaim team coming to the university for in-person training, and the new admin putting in countless support tickets with us as a form of learning. Since this was a new event for us, we reached out to folks personally that we thought might benefit from the training. Though the attendees came from an array of backgrounds, titles, and experiences, we were really pushing to get people that, at the bare minimum, had experienced DoOO at their school for a couple of months. That way they had some familiarity with the platform, had time to come up with questions & knew in advance where their school wanted to take the project.
On Thursday morning, the first day of the workshop, we met folks at Reclaim’s office in Fredericksburg, Virginia. We introduced (or in some cases, reacquainted) ourselves over Panera bagels, and then jumped right into a platform overview at 9 am. Understanding how the platform works and being able to conceptualize how the three main pieces work together is crucial for supporting a community, so we felt like this was a strong start to the workshop. And as Meredith mentioned in her post, having only 6 attendees quickly made the environment feel intimate and comfortable.
After the first session, Tim & Jim took the folks through an in-depth look at WHMCS (client manager) & WHM (server side). The initial homepages of these tools can feel quite intimidating if you haven’t worked with them before, so this felt like the natural next step in the itinerary. In WHMCS, the two covered ‘active’ vs. ‘pending’ orders, deprovisioning accounts, email templates, account ownership, creating Admin roles, and understanding logs & general settings. In WHM, Jim & Tim discussed settings in Installatron, hosting packages, account management, cPanel feature manager, addon domains, storage quotas, and changing domain names. Whew- what a list!
From there I spoke about the actual supporting of DoOO. We’ve learned from early on that Domain of One’s Own is nothing without people that use it, so understanding how to support the community is well over half the battle. I have videos of the talk that I’m currently working to get online, so those should be coming along soon. I covered strategies for approaching a support ticket, top 5 most common support requests & their fixes, unblocking IP addresses in WHM, .htaccess files, HTTP 500 errors, and quick database fixes.
Somehow in the mix of topics and sessions, we were able to fit in a quick lunch– courtesy of Chipotle. :) (Group order links FTW!)
Day two of the workshop was probably my favorite– we picked up right where we left off, continuing to talk through support scenarios by discussing hacked websites and how to clean them up and prevent them in the future. Tim walked folks through strategies, tools to use, and necessary steps to take. I summarized his talk in my blog post, Workshop of One’s Own: Notes on Hacked Site Session.
After that, Meredith spoke on Migrations, Transfers, and Databases. Quite the feat for someone who just joined Reclaim full time in September! She discussed migrating folks to a Domain of One’s Own platform, transferring them off DoOO after graduation, requirements for domain transfers, EPP codes, the lifecycle of domains, the importance of database migration, nameservers, and domain privacy.
Before lunch, I jumped into all things DNS, continuing the theme of supporting Domain of One’s Own. DNS has always felt like a hefty topic for me, so I only covered relevant content regarding the projects of those sitting in the room with us. We explored what DNS actually is and does, types of DNS records, how to edit records from WHM & cPanel, and common DNS errors and fixes to be aware of. I’m hoping to get the video of this session up shortly as well!
With Benny’s Pizza as fuel, Workshop attendees were given a ‘breakout room’-like puzzle during their lunch break. The group had to work together to solve a pretty involved support ticket with fixes that were covered over the last day and a half. They were given 3 escalations or ‘lifelines’ where they could submit a support ticket to ask the Reclaim team for help, but only ended up using 1 lifeline. It was awesome to watch them work together, and to hear their thought process for finding solutions. Everyone had come to the table with different levels of understanding and experiences, so they were able to play on each other’s strengths and weaknesses. When all was said and done, the group of 6 solved the ticket in under an hour by: editing DNS records, correcting a .htaccess file, manually turning off a faulty WordPress plugin, installing an SSL certificate, and editing database files to fix a broken WP dashboard. Not too shabby!
By the afternoon on day 2, everyone was feeling pretty drained but motivated for the last stretch of the workshop. I continued with a discussion about Exit Strategies for graduating students, and spoke on handling migrations, deleting old accounts, and the instructions to give students. From there, Tim conducted the last formal session of the workshop by talking about the potential of APIs in a Domain of One’s Own instance. It was nice to switch gears from more of a formal training of ‘how-to’s’ to an overview of ‘here are things that you could be doing’ approach. He talked through WHMCS hooks, taking advantage of cPanel features without accessing the cPanel interface, additional APIs in Installatron, and different API tools.
The last hour of the workshop was left for an open discussion- we answered any outstanding questions that had arisen, and then tackled more user/project-specific requests.
All in all, it was a jam-packed, successful event. We’re hoping to do these workshops regularly- potentially once a semester- and are so thankful for the folks that decided to come out and help us kick it off. The Reclaim team has already agreed that future workshops should include more interactivities besides the group lunch event on day 2, as they really do help liven things up and allow the group the opportunity to apply what they learned. And though we did take frequent breaks, I’m thinking future events should require additional stretch breaks, or potentially an activity or two where they have to stand up and walk around the room. (Haha!) Regardless of how helpful it can be to dive into dense tutorials on the big screen & follow along on computers, I think we could have used more reminders to get our blood pumping.