I could donate some space on my 4GB linode for you if you'd like.
I'd appreciate it. PM or email me with details.
Topic: [ANNOUNCE] Abe 0.7: Open Source Block Explorer Knockoff - page 51. (Read 221044 times)
I'd appreciate it. PM or email me with details.
n0m4d, thank you.
Confucius, you are welcome to use the URL in the OP, but do not expect as consistent service as you would get from BlockExplorer.com. I run the service for demonstration purposes, the server can not handle BBE's load, the code is not yet as optimal as BBE's, and I will probably move the site to another host/port soon.
Cheers,
John
I could donate some space on my 4GB linode for you if you'd like. Confucius, you are welcome to use the URL in the OP, but do not expect as consistent service as you would get from BlockExplorer.com. I run the service for demonstration purposes, the server can not handle BBE's load, the code is not yet as optimal as BBE's, and I will probably move the site to another host/port soon.
Cheers,
John
much thanks to OP for the open source alternative! Happy to see this flourish and watch the closed source alternatives die off (they were useful for awhile, but really think that where open source alternatives can exist they should)
donation sent
donation sent
Abe or another competing open source, it is a much needed service. Following this thread...
error, I look forward to your GPL competitor. 
Meanwhile, for anyone who wants to customise a public Abe instance without using a Github fork, I've added the following To-Do item:
* Optionally add a link to each page allowing the user to download the
source code and supporting files as a tarfile created on the fly to
satisfy the AGPL.
I won't make this automatic due to security concerns, but I intend to make the new link simply tar up the directory containing abe.py, minus *.pyc and .git, and stream it to the browser as application/x-gtar-compressed or similar. By turning this on and keeping your changes in the directory, you will satisfy the AGPL. [Edit: or I will weaken Abe's license so this satisfies it.] If you implement this before I get to it, feel free to submit a patch or pull request.
I'll also allow config file nesting so that secret configuration such as a database password can be left out.
Meanwhile, for anyone who wants to customise a public Abe instance without using a Github fork, I've added the following To-Do item:* Optionally add a link to each page allowing the user to download the
source code and supporting files as a tarfile created on the fly to
satisfy the AGPL.
I won't make this automatic due to security concerns, but I intend to make the new link simply tar up the directory containing abe.py, minus *.pyc and .git, and stream it to the browser as application/x-gtar-compressed or similar. By turning this on and keeping your changes in the directory, you will satisfy the AGPL. [Edit: or I will weaken Abe's license so this satisfies it.] If you implement this before I get to it, feel free to submit a patch or pull request.
I'll also allow config file nesting so that secret configuration such as a database password can be left out.
n0m4d, thank you.
Confucius, you are welcome to use the URL in the OP, but do not expect as consistent service as you would get from BlockExplorer.com. I run the service for demonstration purposes, the server can not handle BBE's load, the code is not yet as optimal as BBE's, and I will probably move the site to another host/port soon.
Cheers,
John
Confucius, you are welcome to use the URL in the OP, but do not expect as consistent service as you would get from BlockExplorer.com. I run the service for demonstration purposes, the server can not handle BBE's load, the code is not yet as optimal as BBE's, and I will probably move the site to another host/port soon.
Cheers,
John
Great to see more open source efforts!
Will be using your site for now on
Will be using your site for now on
Donated and following.
It's the front end stuff (HTML, CSS, images, etc.) that I really want to customize.
Would you prefer to change things server-side (e.g., through templating) or would client-side scripting work? If you can do it client-side, and you serve your scripts in unprocessed source form with an AGPL-compatible license notice, I won't object. In fact, I'll adjust the output format to suit the task, e.g., XML for Ajax or HTML with data-centric class attributes. And I'll add an optional