Personal tools
In other languages
|
CMSFAQ/ptFrom techmeetSistem Gerenciador de Conteudos Indymedia (CMS)Outras Informacoes sobre o CMS... ... e o Historico da Rede e suas necessidades. Perguntas e Respostas Freqüentes (FAQ)Este FAQ tenta ser um resumo para as discussoes ocorridas nos ultimos anos, para ajudar os/as novos/as desenvolvedores/as a entender as demandas e os objetivos do novo cms. Qual eh o status atual do CMS?Apos dois anos de discussao, nos ainda estamos no rascunho e possuimos um longo estudo sobre todas as possibilidades. Tenha certeza de dar uma olhada em CMSSurveyList Qual foi o resultado desse estudo?No final desse estudo nos nos dividimos em tres grupos
DrupalExiste um grupo que jah esteve bastante ativo de hackers do Drupal, mesmo antes de toda a Discussao em 2006 sobre o novo CMS. Existem alguns CMIs que estao usando o Drupal. Para alguns CMIs menores, o Drupal eh uma boa escolha, jah que eh bastante facil para customizar e nao eh necessario nenhuma experiencia com programacao para customiza-lo. Se voce conhece Drupal, junte-se a galera e ajude. IMC Drupal Development PloneSeria possivel usar o Plone para recriar as funcionalidades atuais de um site feito com Mir. Ele iria ateh mesmo utilizar a mesma quantidade de Recursos do Servidor. Mais informacao sobre o Plone no site wiki do grupo. PHPCake / Novo CMSEsse grupo iria escrever um CMS novo. Quais sao os requesitos para um novo CMS?Existe a pagina CMSWhatWeWant que foi a Lista De Funcoes There is a CMSWhatWeWant Feature Request List from 2006 that will give you a good overview of the needed Front-end functions. However, there are more requirements and ideas for the back-end and the general structure of the CMS. We will try to address these ideas and requirements in this FAQ. Why a new CMS?If you read the Request List, you might get the impression that there are at least 10 CMS out there that would make it possible to create a Indymedia Site. However, there are 4 requirements that no CMS out there can fulfill. 1. A modular structure to separate and spread the functionality over different servers. (The search on one box, the admin on another etc.) 2. Lightweight and fast 3. A Static Producer CMSProducer 4. Content Distribution and Replication Why should i separate the CMS over many servers?First of all, it happens that the State and Police is taking away our servers. Using many servers in many country's makes it harder to take down the hole network at once. Having many different servers with different resources creates a big need for a very flexible CMS to optimize the usage of the servers. Why not use the normal Cache and Back-end Setup?We already use squid, varnishd and mod_proxy together with the old PHP CMS, but this setup is not fail-save at all. As soon as you take down the back-end server, the hole website is down. No cache will continue to deliver a half working website. How would you split a CMS over different servers?You can separate the functionality of a CMS into different categories. a) The output of any kind of static content b) The output of dynamic content like search results or tag clouds c) The interaction for any write process to the site, adding a tag, publishing a article. So the idea is, that each of these modules will continue to work, even if the database and back-end server is down, they should have there own autonomy. How does that look like in detail for......static Output?Output of static content like images should be no problem. Each of these static output servers will have a complete copy of all static files. It would also be possible to create servers based on the type of the content (audio, video, images etc). This gives more flexibility for the usage of the bandwidth and disk space. It is also a big help to have the text content as static .shtml Websites available. This makes it possible to continue to share all informations even if the database and back-end is offline. We had moments in the network where we just edited .shtml files on a couple of mirrors, to keep the users informed about the outage of the back-end server. Try that with any kind of cache. For more informations about this topic, read the Producer Wiki: CMSProducer ...dynamic Output?Well, you run into some problems here, that have a impact on the layout and functionality of the site.
Example: A search would have a index of all articles and there titles, but not the full article. A tag and categories browser would only have the article <> tag mapping
Views |