wiki:WebResources/NewProjectServer

Version 3 (modified by Malte, 8 years ago) (diff)

--

What do we have running and what do we need running, at best at just one server to administer.

Website & Public Info Services, Status: currently diverse

  • Website Drupal unter Apache / PHP 5 (mögl. inkl. neuem Markdown-Wiki als User-Wiki) (RK)
  • DeepaMehta Community Trac unter Apache / Python (DAGNU, Optional?)
  • DeepaMehta Maven Repository (NTC)
  • Static HTML Archive Pages (NTC, Optional)
  • Archived JAMWiki (NTC, Optional)
  • Soundset DM-Instance (NTC, Optional)
  • Nightly Build Server (NONE YET, Optional)

Aim of new, (let's call it the) "Website Server", consolidate administrative efforts and introduce a single-point-of-failure :)

What are your thoughts about the current state here?

DeepaMehta Demo-Server, Status: in preparation

Now, since we got a quite powerful hardware sponsorship which could run such a service, we started thinking of what it needs to do for us.

Short Aim

Show and provide an interactive DeepaMehta User Interface in it's latest state to various interested audiences on http://demo.deepamehta.de.

  • Nothing more, technically.
  • Communicate about the state of the Demo-Server on a bilingual page on our project-website.
  • Do not allow "writing"-access for not-logged in users.
  • Write a News about the new Demo-Server

Possible Development Efforts to support this short aim:

  • Implement a cron-job shuttding-down, resetting and starting up DM
  • Implement a scrip/plugin which introduces e.g "Note" as show-case data after a reset/failure.

The nice thing about such an installation with such minor exteniosn supporting _some permament contents_, we could start to embed just readable topic maps on our website directly from the Demo-Server, e.g. into the "User guide".

Long Aim

Provide a stable and performant to many users as a collaborative community platform with

  • a (comfortable) self-registration process and
  • with content-migration/working updates of the software.