Puppy Linux Discussion Forum

[Q5sys]

[sc0ttman]

Just in case this helps, I have found Hostgator to be great - not only cheap, but friendly, helpful and reliable, and I cannot say that for all of them (GoDaddy, and others, I'm looking at you!)!!

My bandwidth so far this month is 13,914MB and they never hassle me or nag me or anything. I am using around 3GB diskspace apparently, a well.

I'm not hosting much, but know of people who are, they also had no problems. For the price, it is fantastic.

I've got unlimited email accounts, SQL databases (rare), FTP accounts, sub domains, etc, ... And my sites went down only once in 2 years and (only for about 20 mins)...

I checked twitter live feeds for 'hostgator' when it went down, and others like me were shocked - it seems it was the first time for well over year that anyone had any problems with their hosting! Made me feel good.

[Q5sys]

Ive wanted to do this for a while now. but ive had another idea...
I originally was thinking of doing this through a webgui as you can see in the thread. But I'm ok if we can script out the whole thing and make a program that'll run like Pacman in Arch linux or apt-get, etc. Just do pull a file from the site with the file list, grep the file you want... then download the link. etc.
Im sure you get where im going with this. a GTK interface could be made at a later point in time if everything works.

[jemimah]

Ideally, we could just patch the existing ppm. I'm almost ready to work on something like this.

The hosting part should be fairly simple - just ftp access the way smokey01 has his site setup.

The difficult part is finding reliable people to be repo maintainers.

[smokey01]

jemimah,

CatDude and I have created a nice little application that's somewhere between Drop Box and Droper.

It's designed to share files on your own server so you're not locked into a Drop Box account.

Basically it's an icon that sits on the desktop with a smart script in the background. You simply drop a file onto the icon and it will be uploaded to your server space. No need to use an FTP client as a command line version is part of the package. The other nice thing we have incorporated is sorting. Depending on the type of file it will be uploaded to a predetermined directory.

Currently we sort the files into five different directories that includes pets, tarballs, graphics, audio and the rest end up in root. Of course this could be expanded to other files as well.

It's very handy when we are working on something and communicating on Psip. Almost like sitting in the same room.

It would also work very well on Saluki with the xfce window manager as the pet package would be able to put the icon on the desktop during installation.

It won't solve your repository situation but it will make it easy for you to upload to it.

Cheers

[technosaurus]

If only I could find a way to use my Droid as a server...
Like this:http://www.appbrain.com/app/kws-android-web-server/org.xeustechnologies.android.kws
Has anyone tried one for a non-rooted phone.

[Q5sys]

[stu90]

[jemimah]

[Q5sys]

[jemimah]

How well do the external repos work with slacko/lupu/dpup? (I always compile my own stuff so I haven't played with this a lot).

If it already works pretty well then it makes sense (to me) to concentrate on wary/racy since the repos are small and need the most work.

At least to me it makes little sense to spend a lot of time building a puppy out of other distro's packages if you have to recompile the whole repo anyway. Maybe I am missing something here - feel free to set me straight.

Personally, the concept of building puppy from somebody else's repo always made me feel rather unneeded and like the art of finding, hacking, and compiling small packages is largely unappreciated by the majority of users. My point is, there might be more devs if it seemed like devs were actually wanted/needed.

[scsijon]

A thought or two:

This won't be the easiest to setup, but I believe it would make later processing and extending easier!

1- Use a format similar to what barry has done with wary/racy.
in other words, a 2/3 character suffix for base/version specific compiled packages and just i386/i486/i586/i686 for common use packages.

Thus:
pheilix-1.2.9-i486 - would be the pheilix package that SHOULD run on any puppy base that can handle a i486 compiled package! Base Maintainers/Developers would require someone to be responsable to check that it is so as part of their create process!
BUT:
pheilix-1.2.9-w5c - would be the pheilix package that was compiled to run on wary522 / racy522. It may run on others, but no guarantee is provided. If it was pheilix-1.2.9-w5 it would only be certified compatable for earlier wary & racy versions, but MAY run on later wary/racy versions.

I would also like to see a source directory for all compiled packages to be supplied by the initial pet creator as a mandatory requirement, so other base maintainers, could if need be, compile for their own bases without totally restarting from scratch, hopefully with a 'compilers readme' added so any problems/fixes/workarrounds are available for later builders. It would also include later package versions as they are created, but with the notes in earlier versions available, hopefully the later builders work is a little easier.

2- I would prefer something within the PPM package for downloading, something like adding a redline through unsuitable pets or colouring them red, so the user knew they are so. They should not be stopped from installing, just warned that they should think again before doing so! However, where the package is a core package, it should only be available for download, not download and auto-install. How this is done, i'm not quite sure, but there is the BuildingBlock item in the type field, maybe that could be used!

Uploading could be a similar process to that talked about where the new pet & source could be dropped into a box with a question or two with a space for a few lines of information. It should initially go to a hidden area to be checked out and certified by 'a responsable person(s)' for the each of the base(s) it's been submitted against before release.

3- There needs to be something simple to upload on suitable 'mirror servers' to automatically handle the mirror processes. It should not be the responsability of the source server to do anything 'other' than starting the remirror process on the mirroring servers, but the Mirroring servers should be able to handle the rest automatically, preferably with a single email to the mirror server's admin that it has happened or a problem has ocurred. There should also be a written process for setting up a new server!

edit: tpyos!

[smokey01]

I thought iguleder had a good idea with his auto compiling script.

In other words, the repository is just the source. When you select the source it automatically compiles and installs the application.

At least this way the application should always be compatible with your OS.

[Q5sys]

[01micko]

To answer jemimah