Posts by anarking

  • Android application

    for read-only (and this beta version)... $5, or free really would be best for you, that will help you get a user-base, that you need. then the "pro" or write/function version... $15 is probably good. $10 does seem very cheap, but $20 is a bit much until there are more features. although... if you can get those reboot functions in, I will pay $20 :) just my opinion. this is a community open-source project where people are contributing hard work for a common good and for free, so take that into consideration. again, very cool app and happy you've taken the time to make it :) just make sure it's not buggy...

  • Mountpoints will be removed from i-MSCP

    Makes sense. One thing though, is it possible to keep it so that if a domain alias/subdomain is created with a mount point, that if it is later chosen to have redirect, keep the mount point and data?


    Many users like to use this feature temporarily to redirect while they work with files. A lot of people are not good with .htaccess redirects on their own. Not everyone is so technical ;)


    Quote

    Mount points of entities for which an HTTP redirection is already set will be simply deleted (as for in the last i-MSCP versions, when using HTTP redirections, the mount points are not created). Of course, the setup will show a specific warning about such deletion to allow the administrator to do a backup of any data.


    I agree, anything that is created as a redirect, does not need a mount point, but if it already has a mount point and is chosen to redirect, it should keep the mount point, or perhaps ask user (checkbox?) for "permanent redirect", which would delete mount point, or if not checked, leave mount point, so they can remove the redirect later. please don't demand they delete the data.


    A lot of people really like the domain alias/subdomain redirection for temporary uses, it is a good and necessary feature, that is great i-MSCP has it.


    Everything else makes sense, if redirect only, no mount point, and definitely not using the same mount point. Just the "temporary" redirect situation is very important.

  • Multi-Server

    This is for discussing how best to implement Multi-Server capability with internet Multi-Server Control Panel.


    Please feel free to add/discuss anything!


    To make i-MSCP multi-server capable from a customer standpoint, we can deploy many servers, but there needs to be a central login place, that can at least redirect, this can be the first "quick" step...


    Step 1:
    1. Central Control Panel login
    2. Central Webmail login
    3. Central WebFTP login


    To be truly muti-server in the future, these are some functions that come to mind...


    Step 2:
    1. DNS Replication (more than master-> many slaves)
    2. Migrate Customer Data between servers (webfiles, databases, email)
    3. Isolated roles (email server, web server, database server)



    Step 1 Approach:


    1. Central login options (customer login only): New Central Login database is created (admin table, column for serverid). From central server, add new server and db login credentials and it updates central user table periodically (faster), or simply will try all known servers in round-robin until login is validated (slower), and redirects user to new server's control panel after authentication
    or,
    Central server becomes only imscp database server (or specify imscp database location), all child servers use central imscp database (chosen at install), and central db has column added to show server identifier, and after authentication, redirects to new server's control panel.



    2. Central Webmail Login: Roundcube currently has plugin to choose webmail login server based on MX lookup. This is quick fix but not real function. Same options as #1 apply, but with mail_users table in db.


    3. I don't know enough about ajaxplorer and multiple db logins, so probably needs the central db option.



    DNS Needed: Maybe not immediate, but really need complete replication amongst many servers for DNS. There are workarounds for this, and up to 5 servers it's not really needed because of registrar allowing 5 nameserver records for a domain, but it is important functionality.


    I think just having the login central is enough to really be Multi-Server functional right now. All the other features to split apart functionality, migrate, super DNS is all future wishlist.


    Ideas? Comments? What way do you, would you go about these?

  • What next feature you want see in i-MSCP

    i really don't see how just a little ssh or cronjobs are more important than the power of multi-server, as the software is advertised as, but okay ;) i voted for SSH, as that's a valuable feature, but nothing compared to multi-server.


    you say it's possible, then perhaps it's worth it to make it a reality from what is already known. many times i've contemplated switching to ispconfig because it supports it already. their interface is just so terrible haha.


    anyways, i'll start a new thread so we can discuss how it is possible...

  • Android application

    aw, read-only? if i could add/edit, then I would pay. as read-only... sorry.


    but still, very nice work, very happy the program exists, thank you :)


    edit: just saw from your site that you're planning to have the write version available in February, great! when you do, I will buy :)

  • Multiple backups

    i implemented this via cron. created "archive" folder in the backup directory, and the cron moved/renamed the backup files to the archive folder for people that requested archiving. this is why the main backup script had to be changed a bit for me so that it did not delete everything in backup directory.


    i do still have plans to completely overhaul the backup system. i cancelled the idea of uncompressed tar + rsync because pbzip2 is much faster now.


    future, i am thinking of using Duplicity. it is compressed with rsync, and incrementals, so it can archive many days with just the incremental backup sizes. it also has very simple commands for restore (files or db or both), that should be easy to initiate from i-MSCP, as well as create a new backup-on-demand.


    new database entries and backup archiving option for how many days to keep, with duplicity referencing that for backup task.


    this is the best option so far, that I have found. it is a good amount of work I have not gotten around to yet... been working on infrastructure and trying to figure out how to manage i-MSCP while it's not actually multi-server yet and i need it to be haha.


    but Duplicity seems to be the best answer for the future...


    Also, I think backups should count towards disk quota. or perhaps have its own disk quota, that is most preferable.