https://wiki.fsci.in/api.php?action=feedcontributions&feedformat=atom&user=Akshay 2026-05-05T07:00:04Z User contributions MediaWiki 1.44.2 https://wiki.fsci.in/index.php?title=Conference/Meeting&diff=11202 2026-02-12T14:51:55Z

<p>Akshay: backup etherpad as https://phabricator.wikimedia.org/T415237</p> <hr /> <div>Meeting etherpad for FSCIConf0 - https://etherpad.wikimedia.org/p/xMGJGbgqMp-AHjCBlBsV<br /> <br /> == Etherpad archive ==<br /> '''Meeting Number 2'''<br /> <br /> Date: 18th Jan/Sunday)<br /> <br /> Time: 9 PM<br /> <br /> Meeting link: &lt;nowiki&gt;https://meet.fsci.in/fsci-conf-0&lt;/nowiki&gt;<br /> <br /> Agenda items:<br /> <br />    - Discuss inclusion and focus on permacomputing<br /> <br />    - Review potential venues (mini informal bids)<br /> <br />    - Walking into institutes for numbers on end of 10 e-waste<br /> <br /> ---<br /> <br /> '''Meeting Number 1'''<br /> <br /> Date: 8th Nov/Saturday<br /> <br /> Time: 9 PM<br /> <br /> Meeting link: &lt;nowiki&gt;https://meet.fsci.in/fsci-conf-0&lt;/nowiki&gt;<br /> <br /> RSVP:<br /> <br />    YES:<br /> <br />    NO:<br /> <br />    MAYBE:<br /> <br />        - badrihippo<br /> <br />        <br /> <br /> Attendees - Nihal, sahilister, Kiran, Tanzeem<br /> <br /> Agenda Items:<br /> <br />    - Please add here things to discuss<br /> <br />    - Including people from outside tech circles?<br /> <br />    - Sponsorships?<br /> <br /> What should be included in the conference? my suggestions<br /> <br />    - Talks<br /> <br />    - Posters like Timeline<br /> <br />    - Show case various categories of Free Software<br /> <br />    - Linux install point Get your favorite distro installed<br /> <br />    - Libre Phone Point:<br /> <br />     Freeing your phone. <br /> <br />    Showcase Graphene OS etc<br /> <br />    Showcase Free Software apps (even if you aren't ready to switch OSes)<br /> <br />    Get your phone liberated<br /> <br />   - Success stories using Free Software (even examples of established projects, eg. explanation of the Nextcloud business model)<br /> <br />     <br /> <br />    LibrePhone<br /> <br />    GuixOS - (I do know one person other than me, who uses this)<br /> <br />    Open Discussions<br /> <br />   - New Free Software innovations<br /> <br />   - How  AI, ML Data Science should/can be used without compromising freedom and privacy<br /> <br />    - Privacy and Freedom why it should be the primary concern in this age.<br /> <br />    <br /> <br /> Meeting Minutes<br /> <br /> MoM of FSCI Conf planning meet #1<br /> <br /> Attendees: Nihal, Sahil, Kiran, Tanzeem,  Badri, Moksh<br /> <br /> Attendance ratio: N, S, K (4/4 of meeting) T, B (2/4) Moksh (1/4)<br /> <br /> general discussion, sahil mirror, kiran delhi, where is praveen, fiber issue, server in nepal. We have a issue that people acknowledge but don't join. &lt;names&gt;<br /> <br /> S: Recap of previous meet. Today's agenda venue<br /> <br /> K: Recollects how debconf happend. Core team met during other confs and discussed in person.<br /> <br /> S: Debconf next month.  S notes Action Item #1 discuss in Mini Deb Conf mumbai<br /> <br /> N: Suggests moving to a proper note taking platform instead of doing everything in an etherpad. Shows an available option1.<br /> <br /> S: Action #2 noted. Now location<br /> <br /> N: Bengaluru. Pre event before IndiaFOSS. Why- a) FU already doing marketing for IndiaFoss and Side Events b) crowd already gathered there from all over the places. c) rejected proposals of IndiaFOSS, as @nemo mentioned.<br /> <br /> S: Thought of doing it in Feb. IndiaFOSS would be in Sept,<br /> <br /> K: Make poll for location state. Prioritize groundwork, accomodation, cost.<br /> <br /> T: don't want it near IndiaFOSS. <br /> <br /> B: Venue later, general planning now<br /> <br /> S: People don't have enough awareness, we dont have crowd, etc.  We plan location now, and then ask for proposals, bids.<br /> <br /> S: any college contacts for venues?<br /> <br /> N: RV College<br /> <br /> B: Knows someone in Coimbatore<br /> <br /> K: We need ground work<br /> <br /> S: active student community but colleges won't allow during exams<br /> <br /> K: Feb-April<br /> <br /> S: Weekend. diff tracks: BSP&lt; BOF, Show&amp;Tell, Project Tables<br /> <br /> B: We should have a suggested topic list<br /> <br /> K: Formation of teams<br /> <br /> S: logictics, etc from wiki<br /> <br /> S: summarize action items and plan for next meet. Any thing missed, suggestions?<br /> <br /> N: meetings are not required. we can do on chat, asynchronously. <br /> <br /> K: If we have a meeting, then I suggest Tuesdays, Thursdays, Saturdays.<br /> <br /> &lt;nowiki&gt;##&lt;/nowiki&gt; Action ITEM<br /> <br /> * kiran and sahilister will present/meet during MDC Mumbai to get more people in + have physical meeting with others.<br /> <br /> * Nihal to switch us to a PROPER notes<br /> <br /> * didn't pass RFC <br /> <br /> * Reach out to potential venues<br /> <br /> * badrihippo - Coimbatore - (via Women in Tech Collective)<br /> <br /> '''Pointers to know for venues'''<br /> <br /> * Number of attendees: 100+<br /> <br /> * Number of days (and tracks):<br /> <br /> * 2 days<br /> <br /> * 2 tracks (main + secondary) + stalls in hallway<br /> <br /> * Secondary track can have other things like: longer workshops, BoFs<br /> <br /> * Topic: Free Software aligned<br /> <br /> * Timeline: when do we start promoting, when does it happen, etc. - decided based on venue dates.<br /> <br /> * A weekend, in Feb - Apr sometime<br /> <br /> * Organiser: FSCI<br /> <br /> ---<br /> <br /> '''Meeting Number 0'''<br /> <br /> Date: 26th Oct/Sunday<br /> <br /> Time: 9 PM<br /> <br /> Meeting link: &lt;nowiki&gt;https://meet.fsci.in/fsci-conf-0&lt;/nowiki&gt;<br /> <br /> '''RSVP''':<br /> <br />    YES:<br /> <br />        sahilister<br /> <br />        contrapunctus<br /> <br />        <br /> <br />    NO:<br /> <br />        ...<br /> <br />    MAYBE:<br /> <br />        akshay<br /> <br /> '''Agenda Items''': <br /> <br /> (Please name yourself in the pad on top right under &quot;Show the users on this pad&quot; and add things you want discussed in bullets)<br /> <br /> * Introduction of members<br /> <br /> * Name?<br /> <br /> * (Re)articulation of the purpose of above named conf to develop consensus and buy-in among all the participants about what's the conference all about<br /> <br /> * Who all will push (lead) this conf forward as a position of responsibility such that effort doesn't collapse<br /> <br /> * What does local team bidding look like?<br /> <br /> * Communication channel for the organizing team<br /> <br /> * Next steps<br /> <br /> &lt;nowiki&gt;--------&lt;/nowiki&gt;<br /> <br /> MON 26-Oct-2025<br /> <br /> Attendees:<br /> <br />    * sahilister<br /> <br />    * akshay<br /> <br /> sahil explained how DebConf committee works and how minidebconfs were organized earlier.<br /> <br /> akshay said that it might be useful to have a separate remote volunteer team (in addition to conference committee) even though members maybe the same, such that there's greater options for volunteering.<br /> <br /> akshay also expressed hesitance that there's not one person (or one group of people) holding things together.<br /> <br /> Since there were only two attendees, we decided to not make much progress, but rather push for getting more people interested in joining conference committee meetings.<br /> <br /> sahilister to talk to:<br /> <br /> * Nihal<br /> <br /> * contrapunctus<br /> <br /> * Badri<br /> <br /> * Kiran<br /> <br /> * Kishy<br /> <br /> akshay to talk to:<br /> <br /> * Manoj<br /> <br /> * nemo<br /> <br /> * Tanzeem<br /> <br /> * Ujjawal<br /> <br /> * Abhijith<br /> <br /> Things we need to discuss (probably) <br /> <br /> - What're the expectation from the Conf?  (motivational interview)<br /> <br /> - Are they willing to put in time and effort (remotely or on ground)<br /> <br /> - Be active in FSCI chat till we create a new group<br /> <br /> - Don't be afraid of failure. There's always the option of having a remote conference if in a scenario we're not able to pull off a physical conference.<br /> <br /> - What meeting time is suitable for them . Options are:<br /> <br />    - 9 PM Weekends (say Nov 1, 9 PM?) (Or what about Nov 2, 9 PM)<br /> <br />    - Other (Please specify)<br /> <br /> Immediate Tasks:<br /> <br /> - talking to people (sahil, akshay)<br /> <br /> - wiki   -  [[Conference|https://wiki.fsci.in/Conference]]  ?  (sahilister to bootstrap initial pages)<br /> <br /> * - brief bid document<br /> <br /> * - teams and expectation from them - conference comittee, logisitics/venue/registration, content committee,<br /> <br /> * - content committee document - (need to expand/idea dump page), what're the track going to be like. what're we going to talk about. Workshops? invited speakers? hacklab/rooms/hackathons alongside the conf?<br /> <br /> - akshay to update codema and channel about the meeting</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11171 2025-11-12T12:41:39Z

<p>Akshay: add blog link</p> <hr /> <div>[[File:Server rack interconnects work in progress - IMG 3473.jpg|thumb|Server rack interconnects work in progress]]<br /> <br /> When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> &lt;small&gt;⚠ Note: The examples used throughout this article are '''not endorsements'''/suggestions. They're for illustrative purposes with the hope that a novice reader might have heard about that service provider/software and can consequently gain greater understanding.&lt;/small&gt;<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> &lt;small&gt;Note: You might already have seen the term DNS in your router or network settings. It's the same concept. The public/free DNS service you use on your computer is what your browser, etc will use to find out IP addresses of websites you want to visit. But even that DNS service needs to know how to answer a request for your domain. And therefore you need an &quot;authoritative&quot; DNS server which is configured with the right answer. This is often provided by the registrar themselves, but you can also have a service provider different from your registrar be your authoritative DNS server. DNS servers talk to each other. Therefore, even if you have a different DNS server on your router/network, it will eventually ask your authoritative DNS server for the answers.&lt;/small&gt; <br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.<br /> <br /> == Difficulties in self-hosting ==<br /> Although conceptually straightforward, there are some real life scenarios which might make self-hosting a difficult choice for some people.<br /> <br /> === Reliability and uptime ===<br /> Your self-hosted setup can stop working for various reasons. Your site could become popular and get too many requests, thus overloading your server. You could run out of storage space on your disk. You might exceed the bandwidth provided by your internet service provider. Your cloud provider might restart your server without warning, or shut you out because you missed paying.<br /> <br /> You might have to account for these when deploying a super-important service.<br /> <br /> === Data loss and backups ===<br /> There are ways in which you might lose some or all of the data stored by your services. The server could crash. You might accidentally delete some important files or database. You might lose access to the server backend because you lost your SSH credentials and password. The provider might kick you out without warning. Issues during software upgrade could cause data corruption.<br /> <br /> Frequently backing up important data is advised, but also difficult to practice. Some cloud providers have backup services that can do this at an extra cost. There is no guarantee that you'll be able to restore data from backup too.<br /> <br /> === Security ===<br /> There are several bad people on the internet who will try to gain access to your server for various reasons. They might hack into your accounts at your service providers (by phishing, stealing passwords, etc), into your operating system (by brute forcing, etc), or into your software (by exploiting vulnerabilities, etc). Once they gain access to your system they might steal your data and misuse it, hold it ransom, or destroy it altogether. They might run harmful software on your server. They might sometimes even be silently collecting information without revealing their presence.<br /> <br /> When a software maker becomes aware of a security bug (vulnerability) in their software, they fix the bug (patch it) and release new version of their software without the vulnerability. Therefore, keeping your software (operating system and packages) up-to-date with new versions of software is crucial. (But newer versions of software could introduce newer bugs and other incompatibilities).<br /> <br /> Even if the core packages of your software is regularly updated, plugins/extensions can also make the software vulnerable. For example, WordPress has several thousands of plugins (developed by numerous people) and some of these might have vulnerabilities that are not fixed.<br /> <br /> === Cost ===<br /> The more powerful and complicated your self-hosting setup is, the more costly it becomes to run it. You would need to purchase servers with more RAM/storage/CPU and that would be more expensive. You would need larger backups and that'll need to be paid for. And so on.<br /> <br /> While it is possible to find relatively cheap hosting providers, some of them are also more risky. For example, there are complaints about Hetzner kicking users out and deleting their data for missing payments. Some providers (like AWS) offer a free tier to begin with, but at the end of the free tier you would have to pay relatively more (and by then you might have done too much work that is difficult to move to a different provider).<br /> <br /> As costs depend on the exact services you're running, it is difficult to suggest a reasonable cost. But if you are running a simple website or service, it should cost you about ₹500-1500 per month (and not more).<br /> <br /> == Tips ==<br /> <br /> === Prefer static websites when possible ===<br /> A static website refers to a bunch of HTML pages (and the images/styles/javascript required for these) that can be directly served by any web server software. These can be generated by hand (by typing out HTML), by static site generators (like hugo, jekyll), or by using a static export feature of dynamic websites (eg: Simply Static plugin of WordPress, or Static Export feature of NextJS).<br /> <br /> Once generated, these HTML files can be served to any number of users without any change, and without running any other software. Therefore they're simple to host and serve. You can simply use your own web server and point it to the folder containing HTML files to serve the website.<br /> <br /> There are several free hosting providers who host simple HTML static websites too! These include [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages], [https://grebedoc.dev/ Grebedoc], [https://pages.cloudflare.com/ Cloudflare Pages], [https://www.netlify.com/ Netlify], [https://docs.gitlab.com/user/project/pages/ Gitlab Pages], [https://docs.github.com/en/pages Github Pages], etc.<br /> <br /> Although it has limitations in terms of personalization and dynamic features, several websites (including FSCI's website) run as static websites. These are easier to be made secure, can be easily hosted, can be optimized to load very fast, and has several other advantages.<br /> <br /> === Read documentation ===<br /> Some people don't read. And then they make mistakes that they could have avoided if they had read the documentation. One could say that this is a design issue and that the person who did the documentation is to be blamed. But if you want to host services on your own, a mature approach would be to hold yourself accountable in reading documentation. Read documentation. Even if it is long. Even if it will take a long time. Even if you don't understand most of it. (Try to understand more about topics you don't understand). It will help.<br /> <br /> === If you can read the code, you will be able to solve more problems ===<br /> While good documentation is enough to deploy software, documentation is not always complete or correct. If you are able to read the source code you will be able to get an exact answer to various problems you come across. You might be able to spot bugs, report them, and even fix them! Since free software is a collective enterprise, your contribution in this way is welcome and encouraged! (Be mindful about the personal preferences of maintainers, though)<br /> <br /> === LLMs are Stochastic Parrots ===<br /> While LLMs are good at giving you guidance on things about which there is plenty of literature on the internet, many sysadmin tasks are very contextual to your setup (the state of your server and the peculiarities of the software you're dealing with). If you do not know what you're doing, using LLM can be dangerous as they can give generic answers which might not be the best for you. If you do know what you're doing, you probably will be using LLM like a search engine.<br /> <br /> == See Also ==<br /> <br /> * [[Sysadmin roadmap]]<br /> <br /> == External Links ==<br /> <br /> * [https://www.keithcirkel.co.uk/a-playbook-for-hosting-simple-services/ How I host websites] — blog post by Keith Cirkel, engineer at Mozilla</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11170 2025-11-01T14:42:02Z

<p>Akshay: /* Networking */ don&#039;t confuse DNS</p> <hr /> <div>[[File:Server rack interconnects work in progress - IMG 3473.jpg|thumb|Server rack interconnects work in progress]]<br /> <br /> When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> &lt;small&gt;⚠ Note: The examples used throughout this article are '''not endorsements'''/suggestions. They're for illustrative purposes with the hope that a novice reader might have heard about that service provider/software and can consequently gain greater understanding.&lt;/small&gt;<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> &lt;small&gt;Note: You might already have seen the term DNS in your router or network settings. It's the same concept. The public/free DNS service you use on your computer is what your browser, etc will use to find out IP addresses of websites you want to visit. But even that DNS service needs to know how to answer a request for your domain. And therefore you need an &quot;authoritative&quot; DNS server which is configured with the right answer. This is often provided by the registrar themselves, but you can also have a service provider different from your registrar be your authoritative DNS server. DNS servers talk to each other. Therefore, even if you have a different DNS server on your router/network, it will eventually ask your authoritative DNS server for the answers.&lt;/small&gt; <br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.<br /> <br /> == Difficulties in self-hosting ==<br /> Although conceptually straightforward, there are some real life scenarios which might make self-hosting a difficult choice for some people.<br /> <br /> === Reliability and uptime ===<br /> Your self-hosted setup can stop working for various reasons. Your site could become popular and get too many requests, thus overloading your server. You could run out of storage space on your disk. You might exceed the bandwidth provided by your internet service provider. Your cloud provider might restart your server without warning, or shut you out because you missed paying.<br /> <br /> You might have to account for these when deploying a super-important service.<br /> <br /> === Data loss and backups ===<br /> There are ways in which you might lose some or all of the data stored by your services. The server could crash. You might accidentally delete some important files or database. You might lose access to the server backend because you lost your SSH credentials and password. The provider might kick you out without warning. Issues during software upgrade could cause data corruption.<br /> <br /> Frequently backing up important data is advised, but also difficult to practice. Some cloud providers have backup services that can do this at an extra cost. There is no guarantee that you'll be able to restore data from backup too.<br /> <br /> === Security ===<br /> There are several bad people on the internet who will try to gain access to your server for various reasons. They might hack into your accounts at your service providers (by phishing, stealing passwords, etc), into your operating system (by brute forcing, etc), or into your software (by exploiting vulnerabilities, etc). Once they gain access to your system they might steal your data and misuse it, hold it ransom, or destroy it altogether. They might run harmful software on your server. They might sometimes even be silently collecting information without revealing their presence.<br /> <br /> When a software maker becomes aware of a security bug (vulnerability) in their software, they fix the bug (patch it) and release new version of their software without the vulnerability. Therefore, keeping your software (operating system and packages) up-to-date with new versions of software is crucial. (But newer versions of software could introduce newer bugs and other incompatibilities).<br /> <br /> Even if the core packages of your software is regularly updated, plugins/extensions can also make the software vulnerable. For example, WordPress has several thousands of plugins (developed by numerous people) and some of these might have vulnerabilities that are not fixed.<br /> <br /> === Cost ===<br /> The more powerful and complicated your self-hosting setup is, the more costly it becomes to run it. You would need to purchase servers with more RAM/storage/CPU and that would be more expensive. You would need larger backups and that'll need to be paid for. And so on.<br /> <br /> While it is possible to find relatively cheap hosting providers, some of them are also more risky. For example, there are complaints about Hetzner kicking users out and deleting their data for missing payments. Some providers (like AWS) offer a free tier to begin with, but at the end of the free tier you would have to pay relatively more (and by then you might have done too much work that is difficult to move to a different provider).<br /> <br /> As costs depend on the exact services you're running, it is difficult to suggest a reasonable cost. But if you are running a simple website or service, it should cost you about ₹500-1500 per month (and not more).<br /> <br /> == Tips ==<br /> <br /> === Prefer static websites when possible ===<br /> A static website refers to a bunch of HTML pages (and the images/styles/javascript required for these) that can be directly served by any web server software. These can be generated by hand (by typing out HTML), by static site generators (like hugo, jekyll), or by using a static export feature of dynamic websites (eg: Simply Static plugin of WordPress, or Static Export feature of NextJS).<br /> <br /> Once generated, these HTML files can be served to any number of users without any change, and without running any other software. Therefore they're simple to host and serve. You can simply use your own web server and point it to the folder containing HTML files to serve the website.<br /> <br /> There are several free hosting providers who host simple HTML static websites too! These include [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages], [https://grebedoc.dev/ Grebedoc], [https://pages.cloudflare.com/ Cloudflare Pages], [https://www.netlify.com/ Netlify], [https://docs.gitlab.com/user/project/pages/ Gitlab Pages], [https://docs.github.com/en/pages Github Pages], etc.<br /> <br /> Although it has limitations in terms of personalization and dynamic features, several websites (including FSCI's website) run as static websites. These are easier to be made secure, can be easily hosted, can be optimized to load very fast, and has several other advantages.<br /> <br /> === Read documentation ===<br /> Some people don't read. And then they make mistakes that they could have avoided if they had read the documentation. One could say that this is a design issue and that the person who did the documentation is to be blamed. But if you want to host services on your own, a mature approach would be to hold yourself accountable in reading documentation. Read documentation. Even if it is long. Even if it will take a long time. Even if you don't understand most of it. (Try to understand more about topics you don't understand). It will help.<br /> <br /> === If you can read the code, you will be able to solve more problems ===<br /> While good documentation is enough to deploy software, documentation is not always complete or correct. If you are able to read the source code you will be able to get an exact answer to various problems you come across. You might be able to spot bugs, report them, and even fix them! Since free software is a collective enterprise, your contribution in this way is welcome and encouraged! (Be mindful about the personal preferences of maintainers, though)<br /> <br /> === LLMs are Stochastic Parrots ===<br /> While LLMs are good at giving you guidance on things about which there is plenty of literature on the internet, many sysadmin tasks are very contextual to your setup (the state of your server and the peculiarities of the software you're dealing with). If you do not know what you're doing, using LLM can be dangerous as they can give generic answers which might not be the best for you. If you do know what you're doing, you probably will be using LLM like a search engine.<br /> <br /> == See Also ==<br /> <br /> * [[Sysadmin roadmap]]</div>

Akshay https://wiki.fsci.in/index.php?title=Sysadmin_roadmap&diff=11169 2025-10-30T07:02:28Z

<p>Akshay: backup tasks</p> <hr /> <div>If you would like to be a system administrator, or someone who [[Self-hosting|self-hosts]] a lot of software, you need to build sysadmin skills. Here is a suggested learning roadmap for your growth.<br /> <br /> == Hosting ==<br /> <br /> === Host an HTML website ===<br /> Deploy a website made with pure HTML. You could use [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages].<br /> <br /> === Host a static website generated with a static site generator ===<br /> Deploy a website generated with a static site generator like Hugo. Try to automate the deployments using a CI/CD provider.<br /> <br /> === Host a website on your computer at your home ===<br /> Install and configure packages on your computer so that you're able to visit a site on your computer.<br /> <br /> === Make your home-hosted website accessible from the internet ===<br /> You might need to use port forwarding, dynamic DNS, etc. You might sometimes have to contact your ISP to get a static IP or take you out of NAT. As a last resort you might have to piggyback on a cloud server.<br /> <br /> === Host a website on a VPS ===<br /> Get a VPS, and host your own website on it.<br /> <br /> == Deployment ==<br /> <br /> === Deploy a PHP application ===<br /> Deploy a simple php application that doesn't need a database. Something like [https://code.antopie.org/miraty/libreqr/ LibreQR]. You may have to figure out how to use [[PHP-FPM]] and proxy requests to it.<br /> <br /> === Deploy a more complicated PHP application ===<br /> Deploy a slightly more complicated PHP application that requires database. Maybe [https://wordpress.org/ WordPress], or [https://www.mediawiki.org/ MediaWiki]. You might have to figure out which database to use, how to create a database &amp; user and connect the application to it.<br /> <br /> === Deploy a Python/NodeJS/Ruby application ===<br /> Deploy a web application written in Python/NodeJS/Ruby. You might have to figure out how to reverse proxy to the application.<br /> <br /> === Deploy an Docker based application ===<br /> You could choose an application that you've already installed without docker (like [https://hub.docker.com/_/wordpress WordPress]) but this time deploy it using docker. You might have to learn about docker compose too.<br /> <br /> == Maintenance ==<br /> <br /> === Backup an app with its database ===<br /> Create a backup for the wordpress instance (including uploaded images, etc).<br /> <br /> === Restore an app from backup ===<br /> See if your backup can be brought back online.<br /> <br /> === Migrate an app from one server to another ===<br /> Move your app from one computer to another</div>

Akshay https://wiki.fsci.in/index.php?title=Sysadmin_roadmap&diff=11168 2025-10-30T06:48:04Z

<p>Akshay: add deployment challenges</p> <hr /> <div>If you would like to be a system administrator, or someone who [[Self-hosting|self-hosts]] a lot of software, you need to build sysadmin skills. Here is a suggested learning roadmap for your growth.<br /> <br /> == Hosting ==<br /> <br /> === Host an HTML website ===<br /> Deploy a website made with pure HTML. You could use [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages].<br /> <br /> === Host a static website generated with a static site generator ===<br /> Deploy a website generated with a static site generator like Hugo. Try to automate the deployments using a CI/CD provider.<br /> <br /> === Host a website on your computer at your home ===<br /> Install and configure packages on your computer so that you're able to visit a site on your computer.<br /> <br /> === Make your home-hosted website accessible from the internet ===<br /> You might need to use port forwarding, dynamic DNS, etc. You might sometimes have to contact your ISP to get a static IP or take you out of NAT. As a last resort you might have to piggyback on a cloud server.<br /> <br /> === Host a website on a VPS ===<br /> Get a VPS, and host your own website on it.<br /> <br /> == Deployment ==<br /> <br /> === Deploy a PHP application ===<br /> Deploy a simple php application that doesn't need a database. Something like [https://code.antopie.org/miraty/libreqr/ LibreQR]. You may have to figure out how to use [[PHP-FPM]] and proxy requests to it.<br /> <br /> === Deploy a more complicated PHP application ===<br /> Deploy a slightly more complicated PHP application that requires database. Maybe [https://wordpress.org/ WordPress], or [https://www.mediawiki.org/ MediaWiki]. You might have to figure out which database to use, how to create a database &amp; user and connect the application to it.<br /> <br /> === Deploy a Python/NodeJS/Ruby application ===<br /> Deploy a web application written in Python/NodeJS/Ruby. You might have to figure out how to reverse proxy to the application.<br /> <br /> === Deploy an Docker based application ===<br /> You could choose an application that you've already installed without docker (like [https://hub.docker.com/_/wordpress WordPress]) but this time deploy it using docker. You might have to learn about docker compose too.</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11167 2025-10-29T11:30:11Z

<p>Akshay: add image</p> <hr /> <div>[[File:Server rack interconnects work in progress - IMG 3473.jpg|thumb|Server rack interconnects work in progress]]<br /> <br /> When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> &lt;small&gt;⚠ Note: The examples used throughout this article are '''not endorsements'''/suggestions. They're for illustrative purposes with the hope that a novice reader might have heard about that service provider/software and can consequently gain greater understanding.&lt;/small&gt;<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.<br /> <br /> == Difficulties in self-hosting ==<br /> Although conceptually straightforward, there are some real life scenarios which might make self-hosting a difficult choice for some people.<br /> <br /> === Reliability and uptime ===<br /> Your self-hosted setup can stop working for various reasons. Your site could become popular and get too many requests, thus overloading your server. You could run out of storage space on your disk. You might exceed the bandwidth provided by your internet service provider. Your cloud provider might restart your server without warning, or shut you out because you missed paying.<br /> <br /> You might have to account for these when deploying a super-important service.<br /> <br /> === Data loss and backups ===<br /> There are ways in which you might lose some or all of the data stored by your services. The server could crash. You might accidentally delete some important files or database. You might lose access to the server backend because you lost your SSH credentials and password. The provider might kick you out without warning. Issues during software upgrade could cause data corruption.<br /> <br /> Frequently backing up important data is advised, but also difficult to practice. Some cloud providers have backup services that can do this at an extra cost. There is no guarantee that you'll be able to restore data from backup too.<br /> <br /> === Security ===<br /> There are several bad people on the internet who will try to gain access to your server for various reasons. They might hack into your accounts at your service providers (by phishing, stealing passwords, etc), into your operating system (by brute forcing, etc), or into your software (by exploiting vulnerabilities, etc). Once they gain access to your system they might steal your data and misuse it, hold it ransom, or destroy it altogether. They might run harmful software on your server. They might sometimes even be silently collecting information without revealing their presence.<br /> <br /> When a software maker becomes aware of a security bug (vulnerability) in their software, they fix the bug (patch it) and release new version of their software without the vulnerability. Therefore, keeping your software (operating system and packages) up-to-date with new versions of software is crucial. (But newer versions of software could introduce newer bugs and other incompatibilities).<br /> <br /> Even if the core packages of your software is regularly updated, plugins/extensions can also make the software vulnerable. For example, WordPress has several thousands of plugins (developed by numerous people) and some of these might have vulnerabilities that are not fixed.<br /> <br /> === Cost ===<br /> The more powerful and complicated your self-hosting setup is, the more costly it becomes to run it. You would need to purchase servers with more RAM/storage/CPU and that would be more expensive. You would need larger backups and that'll need to be paid for. And so on.<br /> <br /> While it is possible to find relatively cheap hosting providers, some of them are also more risky. For example, there are complaints about Hetzner kicking users out and deleting their data for missing payments. Some providers (like AWS) offer a free tier to begin with, but at the end of the free tier you would have to pay relatively more (and by then you might have done too much work that is difficult to move to a different provider).<br /> <br /> As costs depend on the exact services you're running, it is difficult to suggest a reasonable cost. But if you are running a simple website or service, it should cost you about ₹500-1500 per month (and not more).<br /> <br /> == Tips ==<br /> <br /> === Prefer static websites when possible ===<br /> A static website refers to a bunch of HTML pages (and the images/styles/javascript required for these) that can be directly served by any web server software. These can be generated by hand (by typing out HTML), by static site generators (like hugo, jekyll), or by using a static export feature of dynamic websites (eg: Simply Static plugin of WordPress, or Static Export feature of NextJS).<br /> <br /> Once generated, these HTML files can be served to any number of users without any change, and without running any other software. Therefore they're simple to host and serve. You can simply use your own web server and point it to the folder containing HTML files to serve the website.<br /> <br /> There are several free hosting providers who host simple HTML static websites too! These include [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages], [https://grebedoc.dev/ Grebedoc], [https://pages.cloudflare.com/ Cloudflare Pages], [https://www.netlify.com/ Netlify], [https://docs.gitlab.com/user/project/pages/ Gitlab Pages], [https://docs.github.com/en/pages Github Pages], etc.<br /> <br /> Although it has limitations in terms of personalization and dynamic features, several websites (including FSCI's website) run as static websites. These are easier to be made secure, can be easily hosted, can be optimized to load very fast, and has several other advantages.<br /> <br /> === Read documentation ===<br /> Some people don't read. And then they make mistakes that they could have avoided if they had read the documentation. One could say that this is a design issue and that the person who did the documentation is to be blamed. But if you want to host services on your own, a mature approach would be to hold yourself accountable in reading documentation. Read documentation. Even if it is long. Even if it will take a long time. Even if you don't understand most of it. (Try to understand more about topics you don't understand). It will help.<br /> <br /> === If you can read the code, you will be able to solve more problems ===<br /> While good documentation is enough to deploy software, documentation is not always complete or correct. If you are able to read the source code you will be able to get an exact answer to various problems you come across. You might be able to spot bugs, report them, and even fix them! Since free software is a collective enterprise, your contribution in this way is welcome and encouraged! (Be mindful about the personal preferences of maintainers, though)<br /> <br /> === LLMs are Stochastic Parrots ===<br /> While LLMs are good at giving you guidance on things about which there is plenty of literature on the internet, many sysadmin tasks are very contextual to your setup (the state of your server and the peculiarities of the software you're dealing with). If you do not know what you're doing, using LLM can be dangerous as they can give generic answers which might not be the best for you. If you do know what you're doing, you probably will be using LLM like a search engine.<br /> <br /> == See Also ==<br /> <br /> * [[Sysadmin roadmap]]</div>

Akshay https://wiki.fsci.in/index.php?title=Sysadmin_roadmap&diff=11166 2025-10-29T11:22:25Z

<p>Akshay: </p> <hr /> <div>If you would like to be a system administrator, or someone who [[Self-hosting|self-hosts]] a lot of software, you need to build sysadmin skills. Here is a suggested learning roadmap for your growth.<br /> <br /> == Hosting ==<br /> <br /> === Host an HTML website ===<br /> Deploy a website made with pure HTML. You could use [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages].<br /> <br /> === Host a static website generated with a static site generator ===<br /> Deploy a website generated with a static site generator like Hugo. Try to automate the deployments using a CI/CD provider.<br /> <br /> === Host a website on your computer at your home ===<br /> Install and configure packages on your computer so that you're able to visit a site on your computer.<br /> <br /> === Make your home-hosted website accessible from the internet ===<br /> You might need to use port forwarding, dynamic DNS, etc. You might sometimes have to contact your ISP to get a static IP or take you out of NAT. As a last resort you might have to piggyback on a cloud server.<br /> <br /> === Host a website on a VPS ===<br /> Get a VPS, and host your own website on it.</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11165 2025-10-29T11:05:01Z

<p>Akshay: </p> <hr /> <div>When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> &lt;small&gt;⚠ Note: The examples used throughout this article are '''not endorsements'''/suggestions. They're for illustrative purposes with the hope that a novice reader might have heard about that service provider/software and can consequently gain greater understanding.&lt;/small&gt;<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.<br /> <br /> == Difficulties in self-hosting ==<br /> Although conceptually straightforward, there are some real life scenarios which might make self-hosting a difficult choice for some people.<br /> <br /> === Reliability and uptime ===<br /> Your self-hosted setup can stop working for various reasons. Your site could become popular and get too many requests, thus overloading your server. You could run out of storage space on your disk. You might exceed the bandwidth provided by your internet service provider. Your cloud provider might restart your server without warning, or shut you out because you missed paying.<br /> <br /> You might have to account for these when deploying a super-important service.<br /> <br /> === Data loss and backups ===<br /> There are ways in which you might lose some or all of the data stored by your services. The server could crash. You might accidentally delete some important files or database. You might lose access to the server backend because you lost your SSH credentials and password. The provider might kick you out without warning. Issues during software upgrade could cause data corruption.<br /> <br /> Frequently backing up important data is advised, but also difficult to practice. Some cloud providers have backup services that can do this at an extra cost. There is no guarantee that you'll be able to restore data from backup too.<br /> <br /> === Security ===<br /> There are several bad people on the internet who will try to gain access to your server for various reasons. They might hack into your accounts at your service providers (by phishing, stealing passwords, etc), into your operating system (by brute forcing, etc), or into your software (by exploiting vulnerabilities, etc). Once they gain access to your system they might steal your data and misuse it, hold it ransom, or destroy it altogether. They might run harmful software on your server. They might sometimes even be silently collecting information without revealing their presence.<br /> <br /> When a software maker becomes aware of a security bug (vulnerability) in their software, they fix the bug (patch it) and release new version of their software without the vulnerability. Therefore, keeping your software (operating system and packages) up-to-date with new versions of software is crucial. (But newer versions of software could introduce newer bugs and other incompatibilities).<br /> <br /> Even if the core packages of your software is regularly updated, plugins/extensions can also make the software vulnerable. For example, WordPress has several thousands of plugins (developed by numerous people) and some of these might have vulnerabilities that are not fixed.<br /> <br /> === Cost ===<br /> The more powerful and complicated your self-hosting setup is, the more costly it becomes to run it. You would need to purchase servers with more RAM/storage/CPU and that would be more expensive. You would need larger backups and that'll need to be paid for. And so on.<br /> <br /> While it is possible to find relatively cheap hosting providers, some of them are also more risky. For example, there are complaints about Hetzner kicking users out and deleting their data for missing payments. Some providers (like AWS) offer a free tier to begin with, but at the end of the free tier you would have to pay relatively more (and by then you might have done too much work that is difficult to move to a different provider).<br /> <br /> As costs depend on the exact services you're running, it is difficult to suggest a reasonable cost. But if you are running a simple website or service, it should cost you about ₹500-1500 per month (and not more).<br /> <br /> == Tips ==<br /> <br /> === Prefer static websites when possible ===<br /> A static website refers to a bunch of HTML pages (and the images/styles/javascript required for these) that can be directly served by any web server software. These can be generated by hand (by typing out HTML), by static site generators (like hugo, jekyll), or by using a static export feature of dynamic websites (eg: Simply Static plugin of WordPress, or Static Export feature of NextJS).<br /> <br /> Once generated, these HTML files can be served to any number of users without any change, and without running any other software. Therefore they're simple to host and serve. You can simply use your own web server and point it to the folder containing HTML files to serve the website.<br /> <br /> There are several free hosting providers who host simple HTML static websites too! These include [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages], [https://grebedoc.dev/ Grebedoc], [https://pages.cloudflare.com/ Cloudflare Pages], [https://www.netlify.com/ Netlify], [https://docs.gitlab.com/user/project/pages/ Gitlab Pages], [https://docs.github.com/en/pages Github Pages], etc.<br /> <br /> Although it has limitations in terms of personalization and dynamic features, several websites (including FSCI's website) run as static websites. These are easier to be made secure, can be easily hosted, can be optimized to load very fast, and has several other advantages.<br /> <br /> === Read documentation ===<br /> Some people don't read. And then they make mistakes that they could have avoided if they had read the documentation. One could say that this is a design issue and that the person who did the documentation is to be blamed. But if you want to host services on your own, a mature approach would be to hold yourself accountable in reading documentation. Read documentation. Even if it is long. Even if it will take a long time. Even if you don't understand most of it. (Try to understand more about topics you don't understand). It will help.<br /> <br /> === If you can read the code, you will be able to solve more problems ===<br /> While good documentation is enough to deploy software, documentation is not always complete or correct. If you are able to read the source code you will be able to get an exact answer to various problems you come across. You might be able to spot bugs, report them, and even fix them! Since free software is a collective enterprise, your contribution in this way is welcome and encouraged! (Be mindful about the personal preferences of maintainers, though)<br /> <br /> === LLMs are Stochastic Parrots ===<br /> While LLMs are good at giving you guidance on things about which there is plenty of literature on the internet, many sysadmin tasks are very contextual to your setup (the state of your server and the peculiarities of the software you're dealing with). If you do not know what you're doing, using LLM can be dangerous as they can give generic answers which might not be the best for you. If you do know what you're doing, you probably will be using LLM like a search engine.<br /> <br /> == See Also ==<br /> <br /> * [[Sysadmin roadmap]]</div>

Akshay https://wiki.fsci.in/index.php?title=Sysadmin_roadmap&diff=11164 2025-10-29T10:54:51Z

<p>Akshay: stub</p> <hr /> <div>If you would like to be a system administrator, or someone who [[Self-hosting|self-hosts]] a lot of software, you need to build sysadmin skills. Here is a suggested learning roadmap for your growth.<br /> <br /> == Hosting ==<br /> <br /> === Host an HTML website ===<br /> Deploy a website made with pure HTML. You could use [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages].<br /> <br /> === Host a static website generated with a static site generator ===<br /> Deploy a website generated with a static site generator like Hugo. Try to automate the deployments using a CI/CD provider.</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11163 2025-10-29T10:49:45Z

<p>Akshay: add difficulties and tips</p> <hr /> <div>When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> &lt;small&gt;⚠ Note: The examples used throughout this article are '''not endorsements'''/suggestions. They're for illustrative purposes with the hope that a novice reader might have heard about that service provider/software and can consequently gain greater understanding.&lt;/small&gt;<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.<br /> <br /> == Difficulties in self-hosting ==<br /> Although conceptually straightforward, there are some real life scenarios which might make self-hosting a difficult choice for some people.<br /> <br /> === Reliability and uptime ===<br /> Your self-hosted setup can stop working for various reasons. Your site could become popular and get too many requests, thus overloading your server. You could run out of storage space on your disk. You might exceed the bandwidth provided by your internet service provider. Your cloud provider might restart your server without warning, or shut you out because you missed paying.<br /> <br /> You might have to account for these when deploying a super-important service.<br /> <br /> === Data loss and backups ===<br /> There are ways in which you might lose some or all of the data stored by your services. The server could crash. You might accidentally delete some important files or database. You might lose access to the server backend because you lost your SSH credentials and password. The provider might kick you out without warning. Issues during software upgrade could cause data corruption.<br /> <br /> Frequently backing up important data is advised, but also difficult to practice. Some cloud providers have backup services that can do this at an extra cost. There is no guarantee that you'll be able to restore data from backup too.<br /> <br /> === Security ===<br /> There are several bad people on the internet who will try to gain access to your server for various reasons. They might hack into your accounts at your service providers (by phishing, stealing passwords, etc), into your operating system (by brute forcing, etc), or into your software (by exploiting vulnerabilities, etc). Once they gain access to your system they might steal your data and misuse it, hold it ransom, or destroy it altogether. They might run harmful software on your server. They might sometimes even be silently collecting information without revealing their presence.<br /> <br /> When a software maker becomes aware of a security bug (vulnerability) in their software, they fix the bug (patch it) and release new version of their software without the vulnerability. Therefore, keeping your software (operating system and packages) up-to-date with new versions of software is crucial. (But newer versions of software could introduce newer bugs and other incompatibilities).<br /> <br /> Even if the core packages of your software is regularly updated, plugins/extensions can also make the software vulnerable. For example, WordPress has several thousands of plugins (developed by numerous people) and some of these might have vulnerabilities that are not fixed.<br /> <br /> === Cost ===<br /> The more powerful and complicated your self-hosting setup is, the more costly it becomes to run it. You would need to purchase servers with more RAM/storage/CPU and that would be more expensive. You would need larger backups and that'll need to be paid for. And so on.<br /> <br /> While it is possible to find relatively cheap hosting providers, some of them are also more risky. For example, there are complaints about Hetzner kicking users out and deleting their data for missing payments. Some providers (like AWS) offer a free tier to begin with, but at the end of the free tier you would have to pay relatively more (and by then you might have done too much work that is difficult to move to a different provider).<br /> <br /> As costs depend on the exact services you're running, it is difficult to suggest a reasonable cost. But if you are running a simple website or service, it should cost you about ₹500-1500 per month (and not more).<br /> <br /> == Tips ==<br /> <br /> === Prefer static websites when possible ===<br /> A static website refers to a bunch of HTML pages (and the images/styles/javascript required for these) that can be directly served by any web server software. These can be generated by hand (by typing out HTML), by static site generators (like hugo, jekyll), or by using a static export feature of dynamic websites (eg: Simply Static plugin of WordPress, or Static Export feature of NextJS).<br /> <br /> Once generated, these HTML files can be served to any number of users without any change, and without running any other software. Therefore they're simple to host and serve. You can simply use your own web server and point it to the folder containing HTML files to serve the website.<br /> <br /> There are several free hosting providers who host simple HTML static websites too! These include [https://docs.codeberg.org/codeberg-pages/ Codeberg Pages], [https://grebedoc.dev/ Grebedoc], [https://pages.cloudflare.com/ Cloudflare Pages], [https://www.netlify.com/ Netlify], [https://docs.gitlab.com/user/project/pages/ Gitlab Pages], [https://docs.github.com/en/pages Github Pages], etc.<br /> <br /> Although it has limitations in terms of personalization and dynamic features, several websites (including FSCI's website) run as static websites. These are easier to be made secure, can be easily hosted, can be optimized to load very fast, and has several other advantages.<br /> <br /> === If you can read the code, you will be able to solve more problems ===<br /> While good documentation is enough to deploy software, documentation is not always complete or correct. If you are able to read the source code you will be able to get an exact answer to various problems you come across. You might be able to spot bugs, report them, and even fix them! Since free software is a collective enterprise, your contribution in this way is welcome and encouraged! (Be mindful about the personal preferences of maintainers, though)</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11162 2025-10-29T09:16:46Z

<p>Akshay: add note on non-endorsement</p> <hr /> <div>When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> &lt;small&gt;⚠ Note: The examples used throughout this article are '''not endorsements'''/suggestions. They're for illustrative purposes with the hope that a novice reader might have heard about that service provider/software and can consequently gain greater understanding.&lt;/small&gt;<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11161 2025-10-29T09:11:53Z

<p>Akshay: </p> <hr /> <div>When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> &lt;small&gt;Note: The examples used throughout this article are '''not endorsements'''/suggestions. They're for illustrative purposes with the hope that a novice reader might have heard about that service provider/software and can consequently gain greater understanding.&lt;/small&gt;<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.</div>

Akshay https://wiki.fsci.in/index.php?title=Self-hosting&diff=11160 2025-10-29T08:53:32Z

<p>Akshay: fundamentals of self-hosting</p> <hr /> <div>When you host a web-based software on your own (self), it is called '''self-hosting'''. It could be a simple HTML website, a dynamic PHP blog, or a distributed social network.<br /> <br /> Typically &quot;self&quot; refers to configuration of the software (operating system, packages, database, and so on) alone and the physical server is operated by a cloud provider like AWS, DigitalOcean, or Hetzner. But some people self-host on computers they physically control, in their home or office.<br /> <br /> == Elements of self-hosting ==<br /> <br /> === Networking ===<br /> When you self-host a service, you have to ensure the users/clients are able to reach the service. This requires networking to be setup correctly. <br /> <br /> You would typically need a '''domain name'''. A domain name (like fsci.in) is purchased via a registrar (like NameCheap, Gandi.net) for (mostly) about ₹1000-1500 per year. The ''registrar'' puts your (''registrant'') details in the ''registry'' (which is typically operated by countries or very big companies). And once this is done, you become the proud owner of the domain name. The registration will have to be annually renewed (unless you registered for multiple years). All of this process is overseen by [https://en.wikipedia.org/wiki/ICANN ICANN].<br /> <br /> When you register a domain (say, fsci.in), you are automatically in charge of all subdomains (wiki.fsci.in, videos.fsci.in, meet.fsci.in, etc) and these do not require further registration with the registry. How do you configure these then? That's where '''DNS''' comes in. DNS allows you to specify which server your domains and subdomains should be connected to.<br /> <br /> You can, for example, have fsci.in pointed to 35.185.44.232 with a DNS 'A' record and have wiki.fsci.in pointed to 135.181.250.25 with another DNS 'A' record. That means, when someone types in fsci.in on their browser, the browser will connect to the IP address 35.185.44.232 which will connect it to a '''server''' on the internet with that particular IP address. And similarly when someone types in wiki.fsci.in the browser will connect to a different server, the one with the IP address 135.181.250.25.<br /> <br /> &lt;small&gt;Note: DNS has many types of records. A records are not the only type.&lt;/small&gt;<br /> <br /> === Server ===<br /> The word server has two meanings. It can denote the '''computer''' that's running your services (for example VPS, i.e., Virtual Private Server), it can also mean the '''software''' that's running your services within your server (example: Caddy, Nginx, Apache).<br /> <br /> When you are self-hosting using cloud servers, you would have to purchase a server by paying the service provider (starting from about ₹300-500 per month). The provider (AWS, DigitalOcean, Hetzner, etc) would then run a (virtual) computer in their data center for you. They will ensure that this computer never shuts down, is always kept cool, and is always connected to the internet. They will also provide an IP address for this server. (This is the IP address that you put in your DNS records). <br /> <br /> When your service provider creates the server, they will also install an operating system of your choice (like Debian, Ubuntu, CentOS) on that server. You will be expected to log-in using SSH and configure the server to your liking — installing packages, updating the operating system, editing configuration files, etc.<br /> <br /> Once a user's network request reaches your server, the server software you install (like Caddy, Nginx, Apache) can respond to it based on how it is configured. For a simple HTML site, you typically do not need any additional software and your server software can directly respond with the HTML file from the configured folder. For more complicated services, your server will typically talk to a different software to get the response which eventually gets sent to the user.<br /> <br /> === Software ===<br /> Examples of web-based software include WordPress (for blogging), [[MediaWiki]] (for wiki), [[Loomio]] (for decision making), Prosody (for XMPP instant messaging), NextCloud (for file sharing) and any React/NodeJS/Vue/NextJS/Django/Java/Rails/Flask/etc web projects that you build. Each of these differ in how they are installed and run and you would have to rely on the documentation specific to the software to figure out how to run the service.<br /> <br /> Many software projects use Docker as a uniform way to deploy their software on any operating system. Therefore, many software documentation will ask you to install/run their software using docker. In such cases, there is also often a Docker Compose configuration they recommend which helps with deploying the software and other components it depends on (like the database).<br /> <br /> === Database ===<br /> Most software store important data in a different software – the database (eg: mysql/mariadb, postgresql, sqlite). Some software support using any database software, some require a specific database software.</div>

Akshay https://wiki.fsci.in/index.php?title=PHP-FPM&diff=11159 2025-10-29T07:32:44Z

<p>Akshay: create with common configurations</p> <hr /> <div>PHP-FPM is a gateway that allows running php processes in parallel and processing multiple requests through them. A server (like [[Caddy]] and [[Nginx]]) typically communicates with the php-fpm socket (or port) to render dynamic pages in PHP software (like [[MediaWiki]]).<br /> <br /> == Configuration ==<br /> Configuration folder of php (for version 8.4) is &lt;code&gt;/etc/php/8.4/&lt;/code&gt; (notice the last subfolder changes according to version). Within that folder there are different configurations for different ways php is invoked (apache, cli, fpm). When using PHP-FPM, the configuration in the &lt;code&gt;fpm&lt;/code&gt; folder is what matters.<br /> <br /> Within &lt;code&gt;fpm/pool.d&lt;/code&gt; you find the configurations for different process pools. By default only &lt;code&gt;www.conf&lt;/code&gt; might be present. Within that you can find the path to unix socket (listen), configure number of child processes, etc.<br /> <br /> === Increasing max upload ===<br /> In &lt;code&gt;/etc/php/8.4/fpm/php.ini&lt;/code&gt; set &lt;code&gt;post_max_size&lt;/code&gt; and &lt;code&gt;upload_max_filesize&lt;/code&gt; variables.<br /> <br /> === Increasing workers for www pool ===<br /> In &lt;code&gt;/etc/php/8.4/fpm/pool.d/www.conf&lt;/code&gt; set &lt;code&gt;pm = dynamic&lt;/code&gt; and &lt;code&gt;pm.max_children&lt;/code&gt;, &lt;code&gt;pm.start_servers&lt;/code&gt;, &lt;code&gt;pm.min_spare_servers&lt;/code&gt;, &lt;code&gt;pm.max_spare_servers&lt;/code&gt; as appropriate.</div>

Akshay https://wiki.fsci.in/index.php?title=Wiki.fsci.in&diff=11158 2025-10-29T07:16:30Z

<p>Akshay: link to software</p> <hr /> <div>== Setup ==<br /> [[Caddy]] -&gt; [[PHP-FPM|php-fpm]] -&gt; [[MediaWiki|mediawiki]]<br /> <br /> === Installation ===<br /> Standard installation recommended by official documentation, using tarball and replacing the folder carefully during upgrades.<br /> <br /> === Plugins and skins ===<br /> Non-default plugins and skins are installed directly with git clone and git checkout $RELEASE_VERSION_TAG. They can consequently be updated by doing git fetch and git checkout. <br /> <br /> === Related Services ===<br /> <br /> * [[Codema.in]] runs on the same server</div>

Akshay https://wiki.fsci.in/index.php?title=Caddy&diff=11157 2025-10-29T07:15:08Z

<p>Akshay: create page with common use cases</p> <hr /> <div>Caddy is a server software (like nginx, apache) that has automatic provisioning of https certificates built-in. It is used on several FSCI servers.<br /> <br /> == Links ==<br /> <br /> * [https://caddyserver.com/ Quick start] (scroll down on the official homepage for quickstart)<br /> * [https://caddyserver.com/docs/ Documentation]<br /> <br /> == Features ==<br /> <br /> * Useful default values (for example, php_fastcgi directive by default redirects requests to index.php, reverse_proxy directive by default sets X-Forwarded-* headers, file_server directive by default enforces canonical URLs, etc)<br /> * Automatically generates and rotates TLS certificates (using Let's Encrypt)<br /> <br /> == Common configurations ==<br /> <br /> === PHP sites ===<br /> &lt;syntaxhighlight&gt;<br /> example.com {<br /> root /var/www/example.com<br /> php_fastcgi unix//var/run/php/php-fpm.sock<br /> file_server<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Reverse Proxy ===<br /> &lt;syntaxhighlight&gt;<br /> example.com {<br /> reverse_proxy localhost:8080<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> <br /> === Simple HTML with logging to file ===<br /> &lt;syntaxhighlight&gt;<br /> example.com {<br /> root /var/www/example.com<br /> file_server<br /> log {<br /> output file /var/log/caddy/example.com<br /> }<br /> }<br /> &lt;/syntaxhighlight&gt;<br /> <br /> == Typical workflow ==<br /> <br /> &lt;syntaxhighlight lang=&quot;bash&quot;&gt;<br /> # edit the configuration<br /> sudo -e /etc/caddy/Caddyfile<br /> <br /> # ask caddy to reload configuration<br /> sudo systemctl reload caddy<br /> <br /> <br /> # check status and logs<br /> sudo systemctl status caddy<br /> sudo journalctl -u caddy<br /> &lt;/syntaxhighlight&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=Poddery.com&diff=11156 2025-10-29T06:45:37Z

<p>Akshay: Redirected page to Poddery - Diaspora, Matrix and XMPP</p> <hr /> <div>#REDIRECT [[Poddery - Diaspora, Matrix and XMPP]]</div>

Akshay https://wiki.fsci.in/index.php?title=Fsci.org.in&diff=11155 2025-10-29T06:44:45Z

<p>Akshay: Redirected page to Fsug.in</p> <hr /> <div>#REDIRECT [[Fsug.in]]</div>

Akshay https://wiki.fsci.in/index.php?title=Wiki.fsci.in&diff=11154 2025-10-29T06:42:26Z

<p>Akshay: /* Setup */</p> <hr /> <div>== Setup ==<br /> Caddy -&gt; php-fpm -&gt; [[MediaWiki|mediawiki]]<br /> <br /> === Installation ===<br /> Standard installation recommended by official documentation, using tarball and replacing the folder carefully during upgrades.<br /> <br /> === Plugins and skins ===<br /> Non-default plugins and skins are installed directly with git clone and git checkout $RELEASE_VERSION_TAG. They can consequently be updated by doing git fetch and git checkout. <br /> <br /> === Related Services ===<br /> <br /> * [[Codema.in]] runs on the same server</div>

Akshay https://wiki.fsci.in/index.php?title=Wiki.fsci.in&diff=11153 2025-10-29T06:41:51Z

<p>Akshay: /* Setup */</p> <hr /> <div>== Setup ==<br /> Caddy -&gt; php-fpm -&gt; [[mediawiki]]<br /> <br /> === Installation ===<br /> Standard installation recommended by official documentation, using tarball and replacing the folder carefully during upgrades.<br /> <br /> === Plugins and skins ===<br /> Non-default plugins and skins are installed directly with git clone and git checkout $RELEASE_VERSION_TAG. They can consequently be updated by doing git fetch and git checkout. <br /> <br /> === Related Services ===<br /> <br /> * [[Codema.in]] runs on the same server</div>

Akshay https://wiki.fsci.in/index.php?title=Wiki.fsci.in&diff=11146 2025-10-28T18:17:39Z

<p>Akshay: </p> <hr /> <div>== Setup ==<br /> Caddy -&gt; php-fpm -&gt; mediawiki<br /> <br /> === Installation ===<br /> Standard installation recommended by official documentation, using tarball and replacing the folder carefully during upgrades.<br /> <br /> === Plugins and skins ===<br /> Non-default plugins and skins are installed directly with git clone and git checkout $RELEASE_VERSION_TAG. They can consequently be updated by doing git fetch and git checkout. <br /> <br /> === Related Services ===<br /> <br /> * [[Codema.in]] runs on the same server</div>

Akshay https://wiki.fsci.in/index.php?title=Wiki.fsci.in&diff=11145 2025-10-28T18:16:58Z

<p>Akshay: /* Related Services */ point to instance</p> <hr /> <div>== Setup ==<br /> Caddy -&gt; php-fpm -&gt; mediawiki<br /> <br /> === Installation ===<br /> Standard installation recommended by official documentation, using tarball and replacing the folder carefully during upgrades.<br /> <br /> === Plugins and skins ===<br /> Non-default plugins and skins are installed directly with git clone and git checkout $RELEASE_VERSION_TAG. They can consequently be updated by doing git fetch and git checkout. <br /> <br /> === Related Services ===<br /> <br /> * [[Codema.in|Loomio]] runs on the same server</div>

Akshay https://wiki.fsci.in/index.php?title=Loomio&diff=11144 2025-10-28T18:15:53Z

<p>Akshay: loomio is software, codema.in is the instance</p> <hr /> <div>Loomio is a decision making tool that is developed by a cooperative.<br /> <br /> FSCI hosts its own loomio instance at [[Codema.in]].</div>

Akshay https://wiki.fsci.in/index.php?title=Codema.in&diff=11143 2025-10-28T18:14:09Z

<p>Akshay: Akshay moved page Loomio to Codema.in without leaving a redirect: loomio is the software, codema.in is the item being documented</p> <hr /> <div>[https://freesoftwareindia.org/ Loomio] instance at https://codema.in. Loomio is a '''co'''llaborative '''de'''cision-'''ma'''king platform (hence we're using the name '''codema''') where users can initiate discussions and put up proposals.<br /> <br /> == Setup ==<br /> Caddy -&gt; docker compose from https://github.com/loomio/loomio-deploy/ (with minor modifications to avoid ports 25, 80, 443 from colliding with ports on the host)<br /> <br /> SMTP using Akshay's mail server.<br /> <br /> === Related Services ===<br /> <br /> * [[Wiki.fsci.in]] runs on the same server.<br /> <br /> == Coordination ==<br /> <br /> * Hangout with us in our Matrix room [https://matrix.to/#/#codema:poddery.com #codema:poddery.com]<br /> <br /> === Server Access ===<br /> <br /> Maintained in a private git repo at -&gt; https://git.fosscommunity.in/community/access<br /> <br /> == History ==<br /> Initially some groups were setup on upstream's service: loomio.org <br /> <br /> A loomio instance was also set up later on codema.fsci.org.in<br /> <br /> Later, in December 2019, groups from both these instances were consolidated into a new instance at codema.in. The group data was exported using data export options provided by loomio. Changed the url links in the json data to point towards &lt;nowiki&gt;https://codema.in&lt;/nowiki&gt;. The resulting json files was imported into the new codema instance as described [https://help.loomio.org/en/user_manual/groups/data_export/#import here].<br /> <br /> === Takedown and restoration ===<br /> On 01/02/2019 our server was taken down by [https://scaleway.com Scaleway] quoting payment issues. Payment was failing even after updating the credit card details and following that our server got deleted without proper notifications from Scaleway's side. Fortunately we were provided with a snapshot of the server from which we were able to recover codema to a new server.<br /> <br /> ''Here's a brief description of how codema was recovered after the server take down on 01/01/2019:''<br /> <br /> Under 'Snapshots' tab in the Scaleway dashboard we were provided with the snapshot (backup) of our codema server. A system image was created from this snapshot and it was used to create a new server with similar specifications. We lost our public IP along with the old server, so a new IP was assigned to the server and then updated the DNS A record of codema.fsci.org.in to point to this new IP. Once the server was up loomio was restarted using standard procedure.<br /> <br /> An archive of the old loomio page is available at [[Loomio/Archive_1|Loomio Archive]].<br /> <br /> [[Category: Services]]</div>

Akshay https://wiki.fsci.in/index.php?title=MediaWiki&diff=11142 2025-10-28T18:13:01Z

<p>Akshay: redirect people to wiki.fsci.in</p> <hr /> <div>Mediawiki is a popular wiki software. It powers large wikis like Wikipedia, and also the FSCI wiki which you're reading now. Read more about this wiki on [[Wiki.fsci.in]].<br /> <br /> <br /> <br /> [[Category:Services]]</div>

Akshay https://wiki.fsci.in/index.php?title=Contact&diff=11141 2025-10-28T14:20:58Z

<p>Akshay: remove outdated info</p> <hr /> <div>Find contact details in the footer of FSCI website<br /> <br /> In case you know people in this community personally, you can also find a list of wiki administrators here: [[FSCI Wiki:Administrators]]</div>

Akshay https://wiki.fsci.in/index.php?title=Main_Page&diff=11140 2025-10-28T14:03:40Z

<p>Akshay: new links to list and loomio</p> <hr /> <div>{{Header1}}<br /> {{MainMessage}}<br /> {{BoxLinks}}<br /> {{TextBoxes}}<br /> &lt;center&gt;<br /> {{box1 start}}<br /> [https://lists.fsci.in/postorius/lists/fsci-discuss.lists.fsci.in/ Mailing List]<br /> [[Image:mailman.png|centre|140px|100px]]<br /> {{box2 start}}<br /> [https://codema.in Collaborate]<br /> [[Image:loomio.png|centre|140px|100px]]<br /> {{boxes end}}<br /> &lt;/center&gt;<br /> {{MoreLinks}}</div>

Akshay https://wiki.fsci.in/index.php?title=MediaWiki:Anonnotice&diff=11139 2025-10-28T14:01:38Z

<p>Akshay: distinguish message from content</p> <hr /> <div> To register a new account on this wiki, [https://fsci.in/contact/ contact us]</div>

Akshay https://wiki.fsci.in/index.php?title=MediaWiki:Anonnotice&diff=11138 2025-10-28T13:59:59Z

<p>Akshay: help anons register</p> <hr /> <div>For new accounts, [https://fsci.in/contact/ contact us]</div>

Akshay https://wiki.fsci.in/index.php?title=Codema.in&diff=11137 2025-10-28T13:39:46Z

<p>Akshay: remove historical details and reorganize content</p> <hr /> <div>[https://freesoftwareindia.org/ Loomio] instance at https://codema.in. Loomio is a '''co'''llaborative '''de'''cision-'''ma'''king platform (hence we're using the name '''codema''') where users can initiate discussions and put up proposals.<br /> <br /> == Setup ==<br /> Caddy -&gt; docker compose from https://github.com/loomio/loomio-deploy/ (with minor modifications to avoid ports 25, 80, 443 from colliding with ports on the host)<br /> <br /> SMTP using Akshay's mail server.<br /> <br /> === Related Services ===<br /> <br /> * [[Wiki.fsci.in]] runs on the same server.<br /> <br /> == Coordination ==<br /> <br /> * Hangout with us in our Matrix room [https://matrix.to/#/#codema:poddery.com #codema:poddery.com]<br /> <br /> === Server Access ===<br /> <br /> Maintained in a private git repo at -&gt; https://git.fosscommunity.in/community/access<br /> <br /> == History ==<br /> Initially some groups were setup on upstream's service: loomio.org <br /> <br /> A loomio instance was also set up later on codema.fsci.org.in<br /> <br /> Later, in December 2019, groups from both these instances were consolidated into a new instance at codema.in. The group data was exported using data export options provided by loomio. Changed the url links in the json data to point towards &lt;nowiki&gt;https://codema.in&lt;/nowiki&gt;. The resulting json files was imported into the new codema instance as described [https://help.loomio.org/en/user_manual/groups/data_export/#import here].<br /> <br /> === Takedown and restoration ===<br /> On 01/02/2019 our server was taken down by [https://scaleway.com Scaleway] quoting payment issues. Payment was failing even after updating the credit card details and following that our server got deleted without proper notifications from Scaleway's side. Fortunately we were provided with a snapshot of the server from which we were able to recover codema to a new server.<br /> <br /> ''Here's a brief description of how codema was recovered after the server take down on 01/01/2019:''<br /> <br /> Under 'Snapshots' tab in the Scaleway dashboard we were provided with the snapshot (backup) of our codema server. A system image was created from this snapshot and it was used to create a new server with similar specifications. We lost our public IP along with the old server, so a new IP was assigned to the server and then updated the DNS A record of codema.fsci.org.in to point to this new IP. Once the server was up loomio was restarted using standard procedure.<br /> <br /> An archive of the old loomio page is available at [[Loomio/Archive_1|Loomio Archive]].<br /> <br /> [[Category: Services]]</div>

Akshay https://wiki.fsci.in/index.php?title=Wiki.fsci.in&diff=11136 2025-10-28T13:24:18Z

<p>Akshay: create page with technical details</p> <hr /> <div>== Setup ==<br /> Caddy -&gt; php-fpm -&gt; mediawiki<br /> <br /> === Installation ===<br /> Standard installation recommended by official documentation, using tarball and replacing the folder carefully during upgrades.<br /> <br /> === Plugins and skins ===<br /> Non-default plugins and skins are installed directly with git clone and git checkout $RELEASE_VERSION_TAG. They can consequently be updated by doing git fetch and git checkout. <br /> <br /> === Related Services ===<br /> <br /> * [[Loomio]] runs on the same server</div>

Akshay https://wiki.fsci.in/index.php?title=File:Prav_logo.png&diff=11135 2025-10-28T11:23:45Z

<p>Akshay: Uploaded a work by {{Unknown|author}} from https://codeberg.org/prav/website/src/commit/17592ca8d55e71098080251920133689f2080049/static/images/logo.png with UploadWizard</p> <hr /> <div>=={{int:filedesc}}==<br /> {{Information<br /> |description={{en|1=The logo of Prav Project}}<br /> |date=2023<br /> |source=https://codeberg.org/prav/website/src/commit/17592ca8d55e71098080251920133689f2080049/static/images/logo.png<br /> |author={{Unknown|author}}<br /> |permission=<br /> |other versions=<br /> }}<br /> <br /> =={{int:license-header}}==<br /> {{subst:uwl}}<br /> <br /> This file was uploaded with the UploadWizard extension.<br /> <br /> [[Category:Uploaded with UploadWizard]]</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Test&diff=11134 2025-10-28T11:00:09Z

<p>Akshay: test</p> <hr /> <div>Testing edit</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Test&diff=11133 2025-10-28T10:59:58Z

<p>Akshay: test</p> <hr /> <div>Testing create</div>

Akshay https://wiki.fsci.in/index.php?title=Videos.fsci.in&diff=11108 2025-09-25T09:15:00Z

<p>Akshay: </p> <hr /> <div>== History ==<br /> <br /> === April 2018 ===<br /> On April 15, 2018 a discussion on video hosting kicked off in FSCI matrix channel&lt;blockquote&gt;[https://matrix.to/#/!OBbDJnCnZhQiNQBIcG:matrix.org/$1523784221394MzkgE:poddery.com?via=matrix.org&amp;via=poddery.com&amp;via=tchncs.de raghu kamath]: i am planning to host these videos on my website too, and also provide links to files and video files used<br /> <br /> raghu kamath: &lt;nowiki&gt;https://www.youtube.com/watch?v=Xau4v8OXRyY&amp;list=PLFDnlFYBM_7W9s6TrHBVvAuDE_u8jg0bO&lt;/nowiki&gt;<br /> <br /> raghu kamath: Also i was searching for an peer tube instance in india<br /> <br /> pavi: Someone big should host it. Video is expensive and I wouldnt recommend FSCi do it<br /> <br /> shirish: if anybody knows and has the skillsets, let me know and we can try and figure out.<br /> <br /> shirish: probably even hamara couldn't handle it , it would need quite a bit of cache for it work.<br /> <br /> shirish: end of network kind of thing.<br /> <br /> [...]<br /> <br /> Pirate Praveen: @pavi: I think scaleway.com accounts have unmtered bandwidth<br /> <br /> Pirate Praveen: to scale, it will use p2p<br /> <br /> Pirate Praveen: &lt;nowiki&gt;https://firedragonvideos.com/videos/watch/f669c599-99b0-4b71-9a52-941e509632a7&lt;/nowiki&gt; I started using this instance of peertube<br /> <br /> [...back and forth with pavi about domain name length]<br /> <br /> Pirate Praveen: @pavi: peertube dot co.in is still available, if we want to host<br /> <br /> Pirate Praveen: @raghukamath: if you are interested, we can try setting up one<br /> <br /> pavi: too expensive IMHO. Does anyone have big cash?<br /> <br /> pavi: Maybe we can start a funding drive and see how it goes.<br /> <br /> Pirate Praveen: @pavi: well, the whole point of peertube is that, the server need not take all the load<br /> <br /> pavi: Yes I know. I am still concerned.<br /> <br /> Pirate Praveen: we could start with 3 euro per month plan on experimental basis for a few months<br /> <br /> Pirate Praveen: and decide to continue or not later<br /> <br /> pavi: Wow does it work for peertube?? I am surprised.<br /> <br /> Pirate Praveen: @pavi: why not?<br /> <br /> Pirate Praveen: yes, disk space is going to be an issue<br /> <br /> pavi: @Pirate Praveen: Maybe I am too dumb to learn about the rendering capabilities of a decentralised video server.<br /> <br /> Pirate Praveen: @pavi: it is just bandwidth + storage<br /> <br /> Pirate Praveen: yes, there is a component of video transcoding too<br /> <br /> [...some more back and forth about technicalities]<br /> <br /> pavi: Lets go for it, I can sponsor a server. Someone buy the domain name.&lt;/blockquote&gt;<br /> <br /> === June 2018 ===<br /> There was some issue with YouTube and blender and the link https://www.blender.org/media-exposure/youtube-blocks-blender-videos-worldwide/ was posted on the FSCI matrix channel by raghu kamath&lt;blockquote&gt;[https://matrix.to/#/!OBbDJnCnZhQiNQBIcG:matrix.org/$15294223375602eUPCU:poddery.com?via=matrix.org&amp;via=poddery.com&amp;via=tchncs.de raghu kamath]: yeah, but i feel sad, people need this kind of jolt to move. anyway, i am no better myself. i need to find an instance of peertube. like i said last time we can may be organise something<br /> <br /> Pirate Praveen: @raghukamath: we can run our own if we have some more volunteers<br /> <br /> Pirate Praveen: currenty its just too few people running to many services<br /> <br /> Pirate Praveen on June 20, 2018: if anyone would like to volunteer to setup a peertube instance, let me know. even if you are new, we can mentor you with basic system administration&lt;/blockquote&gt;The discussion channel at https://app.element.io/#/room/#videos.fsci.org.in:poddery.com was created on June 20, 2018 by Pirate Praveen with Harish, pavi, and raghu kamath as members.&lt;blockquote&gt;[https://matrix.to/#/!HgZrJcfVBiMhneKiUv:poddery.com/$1529490063827hwvAz:poddery.com?via=poddery.com&amp;via=matrix.org&amp;via=librem.one Pirate Praveen]: lets run it for a few months on trail basis<br /> <br /> Pirate Praveen: and then decide to make it permanent or not based on the cost and other factors&lt;/blockquote&gt;<br /> <br /> === September 2018 ===<br /> harish [https://matrix.to/#/!OBbDJnCnZhQiNQBIcG:matrix.org/$1536126950219751MzZnc:matrix.org?via=matrix.org&amp;via=poddery.com&amp;via=tchncs.de asks] in the FSCI matrix channel&lt;blockquote&gt;@all<br /> <br /> Can we terminate the test installation of peertube instance which is running @ &lt;nowiki&gt;https://videos.fsci.org.in&lt;/nowiki&gt; ?<br /> <br /> I am summarizing my thoughts behind this question below.<br /> <br /> # Majority of the community is doen't seems to be instrested in this service. there is only one person from this community have tested this service so far. If this is a unnecessary service, we should not waste resource on this.<br /> # if everyone think that this is a necessary service for fsci, then we should move this instance to a &quot;production infrastructure&quot; with better reliability and computing resources. Currently, it is running from one of my personal VPS instance.<br /> &lt;/blockquote&gt;<br /> <br /> === November 2018 ===<br /> This [https://codema.in/d/4SzerK5H/maintenance-of-peertube-instance- codema thread from 2018 November] says:&lt;blockquote&gt;harish k:<br /> <br /> Hi All,<br /> <br /> I am currently maintaining a peertube instance for fsci @ &lt;nowiki&gt;https://videos.fsci.org.in/&lt;/nowiki&gt;<br /> <br /> I would like to handover its responsibility to someone .<br /> <br /> Currently, it is running from my personal Scaleway account.&lt;/blockquote&gt;On 28 Nov 2018 there are a couple of messages in that thread:&lt;blockquote&gt;Tanzeem Mohammad Basheer: I am willing to maintain the peertube instance for fsci. @harishk., please provide guidelines to maintain the server and documents. I am going through the installation documents available online.<br /> <br /> Pirate Praveen: @shine also volunteered (we discussed about it at debutsav.in)&lt;/blockquote&gt;<br /> <br /> === 2020 and later ===<br /> There are some back and forths after that, and 2 years later, on 10 Oct 2020:&lt;blockquote&gt;Akhil: This issue is done and peertube was migrated to an cloud instance in Hetzner. Thanks @harish k and @Tanzeem Mohammad Basheer for the migration and @Kiran S Kunjumon for hosting. Closing the related issue.&lt;/blockquote&gt;In October 2023, a poll was started&lt;blockquote&gt;sahilister:<br /> <br /> FSCI runs a Peertube instance at &lt;nowiki&gt;https://videos.fsci.in&lt;/nowiki&gt; which hosts a few videos &lt;nowiki&gt;https://videos.fsci.in/videos/local?a-state=42&lt;/nowiki&gt;.<br /> <br /> FSCI's Peertube instance hasn't been updated since probably when it was setup back during COVID times. It's running v2.2.0, while latest Peertube is v5.2.1<br /> <br /> It cost ~5.09 euro per month.<br /> <br /> Do we want to keep the instance around as it involves costs and need full planning to bring to latest version.&lt;/blockquote&gt;In the poll the responses were:&lt;blockquote&gt;Snehal Shekatkar: Keep videos.fsci.in around and plan to update<br /> <br /> Although unfortunately I don't have much time and relevant expertise to support this, I can very much support this financially. So I would like to keep it going. If someone is also willing to teach me somewhat, I might try to intermittently take care on the server side.<br /> <br /> <br /> <br /> Pirate Praveen: Keep videos.fsci.in around and plan to update<br /> <br /> If we find new volunteers, we should keep. I think we should keep the poll open for longer (1 week at least and even 2 weeks) and ideally ask around more widely for volunteers before we shut down. Unless we ask explicitly for help people outside the community won't know we need help.<br /> <br /> <br /> <br /> Tanzeem Mohammad Basheer: Keep videos.fsci.in around and plan to update<br /> <br /> Need to update and add videos frequently. Steps should be taken to make the instance more publicly available<br /> <br /> <br /> <br /> Raju Devidas: Sunset videos.fsci.in<br /> <br /> Unless we/someone else are actively/intermmitently using the service, we better sunset the service to actively focus on used services. <br /> <br /> <br /> <br /> Akshay: Keep videos.fsci.in around and plan to update<br /> <br /> I volunteer to update it. But I have no opinion on cost of maintenance. Alternatively we can just keep a static archive of the videos in some server.&lt;/blockquote&gt;The poll was unfortunately settled only on September 14, 2025 with outcome to update. &lt;blockquote&gt;Pirate Praveen: @Akshay are you still interested in updating peertube?<br /> <br /> Akshay: @Pirate Praveen Oh, I don't remember what happened here. I think I volunteered because there were a couple of videos of mine present. I think the same logic applies. I don't have a comment on cost, but I can keep it updated. If it is being sunset I can do the static archive too. Will do later this week&lt;/blockquote&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=Videos.fsci.in&diff=11107 2025-09-25T08:45:47Z

<p>Akshay: add conversation from before dedicated room was created</p> <hr /> <div>== History ==<br /> <br /> === April 2018 ===<br /> On April 15, 2018 a discussion on video hosting kicked off in FSCI matrix channel&lt;blockquote&gt;[https://matrix.to/#/!OBbDJnCnZhQiNQBIcG:matrix.org/$1523784221394MzkgE:poddery.com?via=matrix.org&amp;via=poddery.com&amp;via=tchncs.de raghu kamath]: i am planning to host these videos on my website too, and also provide links to files and video files used<br /> <br /> raghu kamath: &lt;nowiki&gt;https://www.youtube.com/watch?v=Xau4v8OXRyY&amp;list=PLFDnlFYBM_7W9s6TrHBVvAuDE_u8jg0bO&lt;/nowiki&gt;<br /> <br /> raghu kamath: Also i was searching for an peer tube instance in india<br /> <br /> pavi: Someone big should host it. Video is expensive and I wouldnt recommend FSCi do it<br /> <br /> shirish: if anybody knows and has the skillsets, let me know and we can try and figure out.<br /> <br /> shirish: probably even hamara couldn't handle it , it would need quite a bit of cache for it work.<br /> <br /> shirish: end of network kind of thing.<br /> <br /> [...]<br /> <br /> Pirate Praveen: @pavi: I think scaleway.com accounts have unmtered bandwidth<br /> <br /> Pirate Praveen: to scale, it will use p2p<br /> <br /> Pirate Praveen: &lt;nowiki&gt;https://firedragonvideos.com/videos/watch/f669c599-99b0-4b71-9a52-941e509632a7&lt;/nowiki&gt; I started using this instance of peertube<br /> <br /> [...back and forth with pavi about domain name length]<br /> <br /> Pirate Praveen: @pavi: peertube dot co.in is still available, if we want to host<br /> <br /> Pirate Praveen: @raghukamath: if you are interested, we can try setting up one<br /> <br /> pavi: too expensive IMHO. Does anyone have big cash?<br /> <br /> pavi: Maybe we can start a funding drive and see how it goes.<br /> <br /> Pirate Praveen: @pavi: well, the whole point of peertube is that, the server need not take all the load<br /> <br /> pavi: Yes I know. I am still concerned.<br /> <br /> Pirate Praveen: we could start with 3 euro per month plan on experimental basis for a few months<br /> <br /> Pirate Praveen: and decide to continue or not later<br /> <br /> pavi: Wow does it work for peertube?? I am surprised.<br /> <br /> Pirate Praveen: @pavi: why not?<br /> <br /> Pirate Praveen: yes, disk space is going to be an issue<br /> <br /> pavi: @Pirate Praveen: Maybe I am too dumb to learn about the rendering capabilities of a decentralised video server.<br /> <br /> Pirate Praveen: @pavi: it is just bandwidth + storage<br /> <br /> Pirate Praveen: yes, there is a component of video transcoding too<br /> <br /> [...some more back and forth about technicalities]<br /> <br /> pavi: Lets go for it, I can sponsor a server. Someone buy the domain name.&lt;/blockquote&gt;<br /> <br /> === June 2018 ===<br /> There was some issue with YouTube and blender and the link https://www.blender.org/media-exposure/youtube-blocks-blender-videos-worldwide/ was posted on the FSCI matrix channel by raghu kamath&lt;blockquote&gt;[https://matrix.to/#/!OBbDJnCnZhQiNQBIcG:matrix.org/$15294223375602eUPCU:poddery.com?via=matrix.org&amp;via=poddery.com&amp;via=tchncs.de raghu kamath]: yeah, but i feel sad, people need this kind of jolt to move. anyway, i am no better myself. i need to find an instance of peertube. like i said last time we can may be organise something<br /> <br /> Pirate Praveen: @raghukamath: we can run our own if we have some more volunteers<br /> <br /> Pirate Praveen: currenty its just too few people running to many services<br /> <br /> Pirate Praveen on June 20, 2018: if anyone would like to volunteer to setup a peertube instance, let me know. even if you are new, we can mentor you with basic system administration&lt;/blockquote&gt;The discussion channel at https://app.element.io/#/room/#videos.fsci.org.in:poddery.com was created on June 20, 2018 by Pirate Praveen with Harish, pavi, and raghu kamath as members.&lt;blockquote&gt;[https://matrix.to/#/!HgZrJcfVBiMhneKiUv:poddery.com/$1529490063827hwvAz:poddery.com?via=poddery.com&amp;via=matrix.org&amp;via=librem.one Pirate Praveen]: lets run it for a few months on trail basis<br /> <br /> Pirate Praveen: and then decide to make it permanent or not based on the cost and other factors&lt;/blockquote&gt;This [https://codema.in/d/4SzerK5H/maintenance-of-peertube-instance- codema thread from 2018 November] says:&lt;blockquote&gt;harish k:<br /> <br /> Hi All,<br /> <br /> I am currently maintaining a peertube instance for fsci @ &lt;nowiki&gt;https://videos.fsci.org.in/&lt;/nowiki&gt;<br /> <br /> I would like to handover its responsibility to someone .<br /> <br /> Currently, it is running from my personal Scaleway account.&lt;/blockquote&gt;On 28 Nov 2018 there are a couple of messages in that thread:&lt;blockquote&gt;Tanzeem Mohammad Basheer: I am willing to maintain the peertube instance for fsci. @harishk., please provide guidelines to maintain the server and documents. I am going through the installation documents available online.<br /> <br /> Pirate Praveen: @shine also volunteered (we discussed about it at debutsav.in)&lt;/blockquote&gt;There are some back and forths after that, and 2 years later, on 10 Oct 2020:&lt;blockquote&gt;Akhil: This issue is done and peertube was migrated to an cloud instance in Hetzner. Thanks @harish k and @Tanzeem Mohammad Basheer for the migration and @Kiran S Kunjumon for hosting. Closing the related issue.&lt;/blockquote&gt;In October 2023, a poll was started&lt;blockquote&gt;sahilister:<br /> <br /> FSCI runs a Peertube instance at &lt;nowiki&gt;https://videos.fsci.in&lt;/nowiki&gt; which hosts a few videos &lt;nowiki&gt;https://videos.fsci.in/videos/local?a-state=42&lt;/nowiki&gt;.<br /> <br /> FSCI's Peertube instance hasn't been updated since probably when it was setup back during COVID times. It's running v2.2.0, while latest Peertube is v5.2.1<br /> <br /> It cost ~5.09 euro per month.<br /> <br /> Do we want to keep the instance around as it involves costs and need full planning to bring to latest version.&lt;/blockquote&gt;In the poll the responses were:&lt;blockquote&gt;Snehal Shekatkar: Keep videos.fsci.in around and plan to update<br /> <br /> Although unfortunately I don't have much time and relevant expertise to support this, I can very much support this financially. So I would like to keep it going. If someone is also willing to teach me somewhat, I might try to intermittently take care on the server side.<br /> <br /> <br /> <br /> Pirate Praveen: Keep videos.fsci.in around and plan to update<br /> <br /> If we find new volunteers, we should keep. I think we should keep the poll open for longer (1 week at least and even 2 weeks) and ideally ask around more widely for volunteers before we shut down. Unless we ask explicitly for help people outside the community won't know we need help.<br /> <br /> <br /> <br /> Tanzeem Mohammad Basheer: Keep videos.fsci.in around and plan to update<br /> <br /> Need to update and add videos frequently. Steps should be taken to make the instance more publicly available<br /> <br /> <br /> <br /> Raju Devidas: Sunset videos.fsci.in<br /> <br /> Unless we/someone else are actively/intermmitently using the service, we better sunset the service to actively focus on used services. <br /> <br /> <br /> <br /> Akshay: Keep videos.fsci.in around and plan to update<br /> <br /> I volunteer to update it. But I have no opinion on cost of maintenance. Alternatively we can just keep a static archive of the videos in some server.&lt;/blockquote&gt;The poll was unfortunately settled only on September 14, 2025 with outcome to update. &lt;blockquote&gt;Pirate Praveen: @Akshay are you still interested in updating peertube?<br /> <br /> Akshay: @Pirate Praveen Oh, I don't remember what happened here. I think I volunteered because there were a couple of videos of mine present. I think the same logic applies. I don't have a comment on cost, but I can keep it updated. If it is being sunset I can do the static archive too. Will do later this week&lt;/blockquote&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=Videos.fsci.in&diff=11106 2025-09-17T13:51:36Z

<p>Akshay: create page with available histories</p> <hr /> <div>The discussion channel at https://app.element.io/#/room/#videos.fsci.org.in:poddery.com was created on June 20, 2018 by Pirate Praveen with Harish, pavi, and raghu kamath as members.&lt;blockquote&gt;[https://matrix.to/#/!HgZrJcfVBiMhneKiUv:poddery.com/$1529490063827hwvAz:poddery.com?via=poddery.com&amp;via=matrix.org&amp;via=librem.one Pirate Praveen]: lets run it for a few months on trail basis<br /> <br /> Pirate Praveen: and then decide to make it permanent or not based on the cost and other factors&lt;/blockquote&gt;This [https://codema.in/d/4SzerK5H/maintenance-of-peertube-instance- codema thread from 2018 November] says:&lt;blockquote&gt;harish k:<br /> <br /> Hi All,<br /> <br /> I am currently maintaining a peertube instance for fsci @ &lt;nowiki&gt;https://videos.fsci.org.in/&lt;/nowiki&gt;<br /> <br /> I would like to handover its responsibility to someone .<br /> <br /> Currently, it is running from my personal Scaleway account.&lt;/blockquote&gt;On 28 Nov 2018 there are a couple of messages in that thread:&lt;blockquote&gt;Tanzeem Mohammad Basheer: I am willing to maintain the peertube instance for fsci. @harishk., please provide guidelines to maintain the server and documents. I am going through the installation documents available online.<br /> <br /> Pirate Praveen: @shine also volunteered (we discussed about it at debutsav.in)&lt;/blockquote&gt;There are some back and forths after that, and 2 years later, on 10 Oct 2020:&lt;blockquote&gt;Akhil: This issue is done and peertube was migrated to an cloud instance in Hetzner. Thanks @harish k and @Tanzeem Mohammad Basheer for the migration and @Kiran S Kunjumon for hosting. Closing the related issue.&lt;/blockquote&gt;In October 2023, a poll was started&lt;blockquote&gt;sahilister:<br /> <br /> FSCI runs a Peertube instance at &lt;nowiki&gt;https://videos.fsci.in&lt;/nowiki&gt; which hosts a few videos &lt;nowiki&gt;https://videos.fsci.in/videos/local?a-state=42&lt;/nowiki&gt;.<br /> <br /> FSCI's Peertube instance hasn't been updated since probably when it was setup back during COVID times. It's running v2.2.0, while latest Peertube is v5.2.1<br /> <br /> It cost ~5.09 euro per month.<br /> <br /> Do we want to keep the instance around as it involves costs and need full planning to bring to latest version.&lt;/blockquote&gt;In the poll the responses were:&lt;blockquote&gt;Snehal Shekatkar: Keep videos.fsci.in around and plan to update<br /> <br /> Although unfortunately I don't have much time and relevant expertise to support this, I can very much support this financially. So I would like to keep it going. If someone is also willing to teach me somewhat, I might try to intermittently take care on the server side.<br /> <br /> <br /> Pirate Praveen: Keep videos.fsci.in around and plan to update<br /> <br /> If we find new volunteers, we should keep. I think we should keep the poll open for longer (1 week at least and even 2 weeks) and ideally ask around more widely for volunteers before we shut down. Unless we ask explicitly for help people outside the community won't know we need help.<br /> <br /> <br /> Tanzeem Mohammad Basheer: Keep videos.fsci.in around and plan to update<br /> <br /> Need to update and add videos frequently. Steps should be taken to make the instance more publicly available<br /> <br /> <br /> Raju Devidas: Sunset videos.fsci.in<br /> <br /> Unless we/someone else are actively/intermmitently using the service, we better sunset the service to actively focus on used services. <br /> <br /> <br /> Akshay: Keep videos.fsci.in around and plan to update<br /> <br /> I volunteer to update it. But I have no opinion on cost of maintenance. Alternatively we can just keep a static archive of the videos in some server.&lt;/blockquote&gt;The poll was unfortunately settled only on September 14, 2025 with outcome to update. &lt;blockquote&gt;Pirate Praveen: @Akshay are you still interested in updating peertube?<br /> <br /> Akshay: @Pirate Praveen Oh, I don't remember what happened here. I think I volunteered because there were a couple of videos of mine present. I think the same logic applies. I don't have a comment on cost, but I can keep it updated. If it is being sunset I can do the static archive too. Will do later this week&lt;/blockquote&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11081 2025-08-05T12:49:41Z

<p>Akshay: </p> <hr /> <div><br /> &lt;div&gt;[[:Category:Services| Services]] &lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11080 2025-08-05T12:48:44Z

<p>Akshay: </p> <hr /> <div><br /> &lt;div&gt;'''''' &lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11079 2025-08-05T12:48:31Z

<p>Akshay: </p> <hr /> <div><br /> &lt;div&gt;'''[[Special:Statistics|{{NUMBEROFARTICLES}}]]''' &lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11078 2025-08-05T12:48:11Z

<p>Akshay: </p> <hr /> <div><br /> &lt;div&gt;'''[[Special:Statistics|{{NUMBEROFARTICLES}}]]''' Articles are here in English and other languages Arranged in ''[[Special:Categories|Categories]]''&lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11077 2025-08-05T12:47:45Z

<p>Akshay: </p> <hr /> <div>&lt;div&gt;<br /> &lt;div&gt;'''Welcome to Free software Community of India'''&lt;/div&gt;<br /> &lt;div &gt;Free Software Community of India co-ordinates the free software (also open source) related activities in India. &lt;/div&gt;&lt;div&gt;'''[[Special:Statistics|{{NUMBEROFARTICLES}}]]''' Articles are here in English and other languages Arranged in ''[[Special:Categories|Categories]]''&lt;/div&gt;<br /> &lt;div &gt;'''[[Special:Statistics|{{NUMBEROFUSERS}}]]''' Users registered here&lt;/div&gt;<br /> &lt;div &gt;'''[[About|Read More]]'''&lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div &gt;<br /> &lt;div &gt;<br /> *[[:Category:Services| Services]]<br /> *[[Projects]]<br /> *[[:Category:Events| Events]]<br /> *[[Infrastructure]]<br /> *[[BoFs]] <br /> &lt;/div&gt;<br /> &lt;div &gt;<br /> *[[:Category:Communities|Communities]]<br /> *[[:Category:Campaigns|Campaigns]]<br /> *[[SFD|SFD Teams]]<br /> *[[l10n| L10N Teams]]<br /> &lt;/div&gt;<br /> &lt;div &gt;<br /> *[[Email Lists]]<br /> *[[IRC]]<br /> *[[Stuffs]]<br /> *'''[[FAQ]]'''<br /> &lt;/div&gt;<br /> &lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11076 2025-08-05T12:47:20Z

<p>Akshay: </p> <hr /> <div>&lt;div&gt;&lt;div&gt;Some&lt;/div&gt;&lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11075 2025-08-05T12:47:10Z

<p>Akshay: </p> <hr /> <div>&lt;div&gt;&lt;div&gt;&lt;/div&gt;&lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11074 2025-08-05T12:46:20Z

<p>Akshay: Replaced content with &quot; &lt;div&gt;&#039;&#039;&#039;Welcome to Free software Community of India&#039;&#039;&#039;&lt;/div&gt;&quot;</p> <hr /> <div><br /> &lt;div&gt;'''Welcome to Free software Community of India'''&lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11073 2025-08-05T12:45:58Z

<p>Akshay: </p> <hr /> <div>&lt;div&gt;<br /> &lt;div&gt;'''Welcome to Free software Community of India'''&lt;/div&gt;<br /> &lt;div &gt;Free Software Community of India co-ordinates the free software (also open source) related activities in India. &lt;/div&gt;&lt;div&gt;'''[[Special:Statistics|{{NUMBEROFARTICLES}}]]''' Articles are here in English and other languages Arranged in ''[[Special:Categories|Categories]]''&lt;/div&gt;<br /> &lt;div &gt;'''[[Special:Statistics|{{NUMBEROFUSERS}}]]''' Users registered here&lt;/div&gt;<br /> &lt;div &gt;'''[[About|Read More]]'''&lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div &gt;<br /> &lt;div &gt;<br /> *[[:Category:Services| Services]]<br /> *[[Projects]]<br /> *[[:Category:Events| Events]]<br /> *[[Infrastructure]]<br /> *[[BoFs]] <br /> &lt;/div&gt;<br /> &lt;div &gt;<br /> *[[:Category:Communities|Communities]]<br /> *[[:Category:Campaigns|Campaigns]]<br /> *[[SFD|SFD Teams]]<br /> *[[l10n| L10N Teams]]<br /> &lt;/div&gt;<br /> &lt;div &gt;<br /> *[[Email Lists]]<br /> *[[IRC]]<br /> *[[Stuffs]]<br /> *'''[[FAQ]]'''<br /> &lt;/div&gt;<br /> &lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11072 2025-08-05T12:44:40Z

<p>Akshay: </p> <hr /> <div>&lt;div style=&quot;width:100%; background:#fff; margin-top:5em; border:0px solid #BBBBBB; text-align:center; margin-bottom:2em;&quot;&gt;<br /> &lt;div style=&quot;font-size:2.8em; border:none; margin:0; color:#CE3A3A;padding-top:20px;&quot; id=&quot;mf-featuredpicture&quot; title=&quot;Welcome to Free software Community of India&quot;&gt;'''Welcome to Free software Community of India'''&lt;/div&gt;<br /> &lt;div style=&quot;padding-top:10px; font-size:15pt;&quot;&gt;Free Software Community of India co-ordinates the free software (also open source) related activities in India. &lt;/div&gt;&lt;div id=&quot;pagecount&quot; style=&quot;width:100%; text-align:center; font-size:13pt;&quot;&gt;'''[[Special:Statistics|{{NUMBEROFARTICLES}}]]''' Articles are here in English and other languages Arranged in ''[[Special:Categories|Categories]]''&lt;/div&gt;<br /> &lt;div id=&quot;usercount&quot; style=&quot;width:100%; text-align:center; font-size:13pt;&quot;&gt;'''[[Special:Statistics|{{NUMBEROFUSERS}}]]''' Users registered here&lt;/div&gt;<br /> &lt;div id=&quot;more&quot; style=&quot;width:100%; text-align:center; font-size:13pt;margin-top:15px;&quot;&gt;'''[[About|Read More]]'''&lt;/div&gt;<br /> &lt;/div&gt;<br /> &lt;div class=&quot;home-flex-container&quot;&gt;<br /> &lt;div class=&quot;flex-item&quot;&gt;<br /> *[[:Category:Services| Services]]<br /> *[[Projects]]<br /> *[[:Category:Events| Events]]<br /> *[[Infrastructure]]<br /> *[[BoFs]] <br /> &lt;/div&gt;<br /> &lt;div class=&quot;flex-item&quot;&gt;<br /> *[[:Category:Communities|Communities]]<br /> *[[:Category:Campaigns|Campaigns]]<br /> *[[SFD|SFD Teams]]<br /> *[[l10n| L10N Teams]]<br /> &lt;/div&gt;<br /> &lt;div class=&quot;flex-item&quot;&gt;<br /> *[[Email Lists]]<br /> *[[IRC]]<br /> *[[Stuffs]]<br /> *'''[[FAQ]]'''<br /> &lt;/div&gt;<br /> &lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11071 2025-08-05T12:43:30Z

<p>Akshay: </p> <hr /> <div>[https://lists.fsci.org.in/postorius/lists/fsci-discuss.lists.fsci.org.in/ Mailing List]<br /> [[Image:mailman.png|centre|140px|100px]]<br /> [https://www.loomio.org/g/esPoQ4S0/fosscommunity-in Collaborate]<br /> [[Image:loomio.png|centre|140px|100px]]<br /> <br /> &lt;div&gt;&lt;/div&gt;</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11070 2025-08-05T12:40:35Z

<p>Akshay: </p> <hr /> <div>[https://lists.fsci.org.in/postorius/lists/fsci-discuss.lists.fsci.org.in/ Mailing List]<br /> [[Image:mailman.png|centre|140px|100px]]<br /> [https://www.loomio.org/g/esPoQ4S0/fosscommunity-in Collaborate]<br /> [[Image:loomio.png|centre|140px|100px]]</div>

Akshay https://wiki.fsci.in/index.php?title=User:Akshay/Main_page&diff=11069 2025-08-05T12:40:19Z

<p>Akshay: </p> <hr /> <div>{{box1 start}}<br /> [https://lists.fsci.org.in/postorius/lists/fsci-discuss.lists.fsci.org.in/ Mailing List]<br /> [[Image:mailman.png|centre|140px|100px]]<br /> {{box2 start}}<br /> [https://www.loomio.org/g/esPoQ4S0/fosscommunity-in Collaborate]<br /> [[Image:loomio.png|centre|140px|100px]]<br /> {{boxes end}}</div>

Akshay