User Tools

Site Tools


Coopon Inhouse Infrastructure

Inorder, to use certain services helping to run Coopon itself are essential and required to enable its technical and non-technical members alike to participate in day to day activities. This Wiki is one such example where we collaborate together to document our efforts, create accountability, track our status, etc…

The following services are being run in the Coupon Server - an instance of Digital Ocean droplet server, mostly funded by Mr.Kamalavelan & Mr.Prasanna Venkatesh.

Purpose/Service Source Project Service Link Status
Wiki Doku Wiki Coopon Wiki Operational, Used
Productive Chat Zulip Chat Coopon Zulip Not Used
Meta Management Metabase Not yet Deployed
Web Server Nginx Used
Mail Server Mail in a Box Mail Server (doc) Operational, Used
Database Servers Maria, PostGIS Used
Application Server Mindmap Used. Seldom
Application Server Uauto/Transfed Operational

For now the git repositories for the development are hosted on Gitlab. Zulip Chat, connects with Gitlab notifications, to enable streamlined - informed collaboration between members contributing to any particular project.

The cost of running the server accounts to around Rs. 1000/- per month - as informed earlier - beared by Kamalavelan mostly. Any round robin or mutual sharing the cost might be fruitful.

Avoiding Vendor Lockin

As a small business alternative model, generating a scalable, copyable business model such that other communities, coops, can kickstart a similar social business model depends upon what kind of tools, frameworks are used with what kind of licensing terms, community support, stability, features, portability, extensibility, etc… Along with other such features, one of the important property that an infrastructure, framework, tools must not have is vendor-lockin. For instance, one can learn from this article, why it is necessary to avoid such locks for building a local first, sustainable coop, with almost no capital expenditure in hand.

It is very much equally important to weigh the reasons for social, economic, market conditions against the technology available in the market. One must understand every product is a project of labour. Ownership and enclosure tactics through cultural, legal structures creates injustice. Thus clearly vendor lock-in is a model to monopolize every user and service to a particular giant forever, the business will oscillate between its ethical goals and dependency factors to serve its user base without interruption, even if decided to migrate. Thus deciding before deploying the service is necessary and everyone must understand the reasons so that a common consensus can be reached.

Tools Capably Used by Coopon

Since we evolved from Free Software & Hardware movments, flocked together now to create alternative-economic model platform for collective self sstenance, our tool and technological spectrum must also align and bear towards community generated and managed software, hardware design, or atleast for the tools that have beter community support. We are also proud about using Free Software tools. Fortunately we are in an era, where openness, transparency, accessibility are relatively abundant than past decade. We avoid using proprietary software/hardware almost at all times. Only during situations of dire consequences that would affect the cooperativ,e we compromise our operating philosophy if no other neighbours, friends, relatives does not have a proprietary technology.

The purpose of this page is to equip and augment learning/skill development through planned organization, reducing the information overload while exploring to study and program information. Although Coop members can help learn or mentor newmembers, about any technology or process that they are already aware of, it is overwhelming to expect complete hand dragged guidance from the coop. All the necessary tools, links, licenses are provided for those who are willing to learn. It is expected to self learn with available listed resources here.

Feel free to edit the deprecated links, add new tool, process, tech. We are trying to keep a learnable infrastructure instead of a black box model. This reduces the skill shock, thus easing the learning curve, save time in exploring the diverse set of tools - for the newcomers. Again this is a cooperative effort to keep the knowledge base update.

No. Field Purpose Collective Skill
1. Programming Compute * *
2. Coding Development/Coding * * * * *
3. Desktop Desktop App. Development * *
4. Mobile Mobile App. Development * *
5. Web Web App. Development * * * * *
6. Database Database Management * *
7. Communications Communications & Signal Processing * *
8. Instrumentation Embedded System Development * *
9. UX & UI Design Interaction Designing * * * * *
10. Graphics Graphic Designing * * * * *
12. Typesetting Typography Designing * * * *
13. GIS/RS GIS/RS Design, Development & Analysis * * *
14. NLP NLP, Speech, Text, Linguistics, Transliterate *
15. Statistics & Machine Learning Statistics & Learning * *
17. Health Care Health Care System *
18. Finance Finance/Cash Mgmt. * *
19. Publishing Publishing Frameworks * *
20. Digital Humanities Digital Humanities * *

Reusable Resources

We know that cooperative self sustenance and mutual benefit will come from sharing labour, skill and knowledge. And to be as independent as possible we pool together individually acquired digial resources manifesting art, technology, knowledge in terms of digital files, code repositories, which will be immensely helpful in designing and developing tools and applications that are interactive, engaging, pleasing with aesthetics and ergonomics. Thus importance must be equally provided to tools and resources of both art and technology creating equal parts of developer and designer in a member.

  1. Design Resources (UI, UX Components)
  2. Code Snippets, Templates
  3. Document Templates
infra.txt · Last modified: 26/03/2020 11:49 (external edit)