3/16/2024 0 Comments Comment installer whatsappOn the left navigation bar, select Storage > PoolsĮxpand your primary storage pool. For those of you who do want to adopt it, and are confused about how to go about it, I’ll explain it below. I’m sure many of you will have organised your datasets differently – that’s fine this has worked well for me, feel free to adopt it, or don’t it will be the context in which I explain this guide though. A number of other datasets are created within the iocage dataset, however these aren’t particularly relevant to this guide, so if you see them and wonder if they’re supposed to be there don’t stress, they are. Specifically, in jails > jailname, or in this case jails > nextcloud. This is created automatically when you create a jail, so you don’t need to worry about doing anything here, however it is important to note that this is where the local storage for your iocage jails is held. The remaining dataset is the ‘iocage’ dataset. As can be seen, there is a dataset named ‘nextcloud’, which then contains ‘config’, ‘themes’ and ‘db’ datasets for the required information. To organise this, I’ve created an ‘app’ dataset which holds a dataset for each jail I create. I’ve stored the remaining data in their own datasets on my jailhouse pool. It’s important that this is on your primary storage pool so that it can grow in size as required. In the above structure, the ‘cloud’ directory represents the data directory this is where all of your files will be stored. Note that this doesn’t serve as a backup for the purposes of upgrading, however it will afford you some ability to nuke the jail without risking the loss of data. This means that if for whatever reason your Nextcloud jail has been broken or deleted, you should be able to restore back to your previous configuration with minimal hassle. Therefore, it makes sense to make this data independent of the jail (more on this later). Īccording to the Nextcloud Documentation, there are four things required to restore a Nextcloud installation: The final dataset structure I have is as follows: The second, “jailhouse”, is a 500GB Samsung SSD, and is the pool I store all of my jails on so that they benefit from the faster IO operations an SSD affords. One, titled “vault”, is my primary storage pool, comprised of 6x4TB WD Red drives. One thing I’ve noticed a lot of people get hung up on is dataset structure, so to be explicit, I’ll describe my configuration. A disclaimer to this is that I am by no means an expert, and am still learning, so if you spot any errors or have any suggestions please leave a comment below! With this in mind, my aim is to be complete as possible with the information I provide, and also to provide some context about why certain tasks are being undertaken rather than just direction on which commands to run. The target audience for this guide is the person with very little exposure to the command line in either Linux or FreeBSD. A lot of this is adapted from dureal99d’s post on the same topic, who did a great job at explaining the process, however it discussed the installation of Nextcloud 13, and the certificate installation process was unsuccessful for me so my thought is to share my learnings to save the next person the trouble. My aim here is to be as explicit as possible about the process I followed so that even a relatively new beginner is able to follow them. I’ve recently been through the process of standing up my own personal cloud server, and found that there were a few points of difficulty not directly covered in existing guides on the topic (such as improving security/hardening the server), and a number of the guides on the topic suggested implementing bad practices, such as the use of mod_php (I’ll be using php-fpm!).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |