Paul Hammant transcribed 7.9K bytes: > Are you sure there's not some no-frills way of getting at what used to be > on Google code - e.g. > https://code.google.com/archive/p/majesticuo/source/default/source ?
Well, it's still there on google.com. Surprisingly, as I thought they'd just cut off connections at the date they targeted to shut down the hosting. So you can still get the master, export to github, export to a real git hosting, etc. So https://storage.googleapis.com/google-code-archive-source/v2/code.google.com/majesticuo/source-archive.zip works and https://code.google.com/export-to-github/export?project=majesticuo will do the export to GitHub. I just wanted to express under the assumption that it was already offline, that sometime it can be difficult to find the "real" developers repository with all these exports. > On Thu, Mar 30, 2017 at 7:01 AM, ng0 <contact....@cryptolab.net> wrote: > > > Paul Hammant transcribed 4.8K bytes: > > > Thanks Joe, thanks Stephen. > > > > > > Joe, > > > > > > Here's a "seatmap" app I made using CouchDB - > > > http://paulhammant.com/2015/12/21/angular-and-svg-and-couchdb/. It works > > > with CORS enabled. In the new Serverless era ( > > > https://martinfowler.com/articles/serverless.html - Mike is a buddy and > > > former colleague of mine) things like CouchDB make perfectly usable > > > "backend as a service" (BaaS) technologies. CouchDB allows anon access as > > > well as logged in users (if so configured). In a sophisticated BaaS > > > solution you'll probably want both and something fine grained to support > > > that in the BaaS platform ..... which probably means some TH1 fu on the > > > server side. > > > > > > Stephen, > > > > > > Nice achievement and great document on the JSON-api usage (and challenges > > > you faced). <cough> should be in markdown under source-control of course > > > </cough>. What was the name of your GoogleCode application? They all got > > > auto-moved to Github at some point. I'm example orientated and can only > > > > If only.. You had the option to export them at free will. That sadly > > also means that in the cases where upstream developers went on hiatus > > long enough to miss the shutdown we now have to search for the correct > > upstream. libmp4v2 is one of the packages which makes our job as package > > maintainers harder than it has to be. > > > > > really make leaps in understanding after looking a tight solutions :) > > > > > > - Paul > > > > > > On Wed, Mar 29, 2017 at 10:45 PM, Joe Mistachkin <sql...@mistachkin.com> > > > wrote: > > > > > > > > > > > If you compile Fossil with TH1 docs & hooks support and with Tcl > > > > integration > > > > enabled (like I compile it), it makes quite a reasonable server for > > running > > > > server-side scripts written in TH1/Tcl. > > > > > > > > -- > > > > Joe Mistachkin @ https://urn.to/r/mistachkin > > > > > > > > _______________________________________________ > > > > fossil-users mailing list > > > > fossil-users@lists.fossil-scm.org > > > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > > > > > > _______________________________________________ > > > fossil-users mailing list > > > fossil-users@lists.fossil-scm.org > > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > > _______________________________________________ > > fossil-users mailing list > > fossil-users@lists.fossil-scm.org > > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
