Sep 042014
 

Many thanks to GNUtransfer for lending us a VPS and other resources to write this article.

In this article we will show how to use the package litecoind-init for debian wheezy amd64 available in our repository

This is the litecoind package for debian wheezy amd64 compiled with downloaded sources from git repository https://github.com/litecoin-project/litecoin and a script in init.d to start and stop it.

The package has a start and stop script in /etc/init.d

Continue reading »

Sep 042014
 

Many thanks to GNUtransfer for lending us a VPS and other resources to write this article.

In this article we will show how to use the package bitcoind-init for debian wheezy amd64 available in our repository.

NOTE: We have called this package “bitcoind-init” to avoid conflicts with “bitcoind” package available in Debian repositories.

This is the bitcoind package for debian wheezy amd64 compiled with downloaded sources from git repository https://github.com/bitcoin/bitcoin.git and a script in init.d to start and stop it.

The package has a start and stop script in /etc/init.d

Continue reading »

Sep 022014
 

Many thanks to GNUtransfer for lending us a VPS and other resources to write this article.

We have created a debian wheezy amd64 repository to allow the installation of the following packages:

  • bitcoind-init
  • litecoind-init
  • p2pool-init
  • xen-4.4

In this article we will see how to add the repository to a Debian Wheezy amd64 installation

Continue reading »

Oct 282013
 

There is a first phase in version 2.0 development which is important because it has to do with a brand new code, designed to be flexible and adaptable.

The crowdfunding project proposes the creation of a DEB package compatible with Debian GNU/Linux. In practice this will be a group of installable packages to cover different needs.

A practical example

It is instructive to give a practical example of a possible use of the program to understand its operation.
The most basic setup of GNUPanel 2.0 will require at least of two packages: gnupanel-master and gnupanel-slave (these names can be modified).

A possible scenario could consist of two servers. Two reliable virtual servers for instance could be a very good choice because of the redundancy, economy, scalability and flexibility for migration or recovery tasks.

The diagram shows a master server or main server hosting the database, the DNS system and both interfaces, ADMIN and USER.
Another server called slave will host different hosting accounts from different users or customers.

GNUPanel_2_arch

All hosting plans can be defined from the ADMIN interface. There could be some of them allowing to host a single domain name, others allowing to host hundreds.
Each potential user or client has immediate access to the system’s USER interface after completing an email registration form. Once inside the system he can choose the best hosting plan available and order it. As soon as payment is completed domain names can be added to the account, all the process is fast and automatic.

It is easy to note that this working model allows web hosting plans creation but there is no RESELLER interface.

The RESELLER interface will be done in a second phase and this is so to allow a shorter development time frame to get a functional and installable version. A website development company for example, that host and maintain all its production, can use the control panel as soon as first phase is completed no matter if RESELLER interface is ready or not.