I just tried
git clone --depth=1 --branch=R-2.14.6 --recursive --shallow-submodules
https://github.com/web2py/web2py.git
and I got this error:
error: no such remote ref 60e97e7cfd1da98f3cf38b2023965226d42e5e5b
Fetched in submodule path 'gluon/packages/dal', but it did not contain
60e97e7cfd1da98f3cf38b2023965226d42e5e5b. Direct fetching of that commit
failed.
Also tried it without --shallow-submodules but got the same result.
On Thursday, July 28, 2016 at 10:37:32 AM UTC-3, Niphlod wrote:
>
> These are all fair points, and I tried to change it over the years by
> myself.
> Unfortunately, everything I attempted failed, but let's "mitigate" point
> by point.
> The uttely big disadvantage in retrieving web2py is the lack of a web2py
> package on pypi. Would that - finally - be available, pretty much all of
> the pain-points would be obliterated.
> In the meantime, please be "reassured" that the current url-scheme to
> download the latest stable won't change. Massimo is behind every "cooked"
> release and he's the only one that could change that. I assume that - if
> ever - it SHOULD change, there will be a pretty big notice everywhere.
>
> As for pydal being an external package, we weighted the pros and cons and
> the submodule won. Unfortunately, it's github that is "limiting" the
> otherwise good feature of being able to download the archive of a release
> containing submodules: as you pointed out, the releases don't contain the
> submodule.
>
> The same pros and cons would surface extrapolating admin, welcome and
> examples app out of the web2py release... for the moment web2py IS treated
> much more like a "download the zip, extract it and execute" entity rather
> than a proper python package. In the latter "vision", we should only have a
> "web2py" package providing "gluon", with a hard requirement on "pydal"
> (fortunately it is yet a proper package), and maybe a bootstrap script
> fetching the apps from a zip or a repo (apps are not that "packageable" as
> python packages either way).
>
> Please also consider that no-one in a serious production script relies on
> external services being available at deploy-time :-P
>
> I'd though urge you to abandon the "let's fetch an archive, extract and
> manipulate it" over preparing your own and upload it every time you need to
> do something on your production servers, you can "modernize" your way of
> retrieving something similar to the web2py zip release simply using the
> github repo... all you'd need in addition to the current tooling is git,
> which is totally not a far-fetched ipothesis, even on production servers.
>
> git clone --depth=1 --branch=R-2.14.6 --recursive
> https://github.com/web2py/web2py.git
>
> would create a nice dir with web2py and pydal .
>
> Bonus points, if you have git >= 2.9.0 , you can issue
>
> git clone --depth=1 --branch=R-2.14.6 --recursive --shallow-submodules
> https://github.com/web2py/web2py.git
>
> to save further bandwith (until 2.9.0 submodules are fetched in their
> entirety, not as "shallow" ones)
>
> On Thursday, July 28, 2016 at 2:26:19 PM UTC+2, Alex wrote:
>>
>> I'm using deployment scripts (which check dependencies and webp2y
>> version, perform updates if necessary, etc.) for easy deployment of my
>> applications and there are a few pitfalls with web2py. It would be good if
>> this could be resolved and thus make web2py more professional.
>>
>> Sometime ago you made an own module of DAL which I think is good because
>> DAL is really great and should be used in other projects as well. The
>> problem is that you reference DAL as a submodul in the git repository of
>> web2py. This makes it hard to get a working snapshot of web2py. E.g. look
>> here for the latest releases:
>> https://github.com/web2py/web2py/releases
>> downloading a release from here only gives a broken release because
>> gluon/packages/dal is empty. The same happens when I checkout web2py
>> directly from github.
>> As a workaround I download the release from "
>> http://web2py.com/examples/static/<version>/web2py_src.zip" which is
>> complete. But I don't actually know if this download is stable (since it's
>> in the examples directory). If you should ever decide to remove the
>> downloads from there all my deployments will be broken.
>>
>> * Solution: insert DAL code of specific DAL release into web2py
>> repository and not just a reference. Upgrade the DAL code once in a while
>> (e.g. for new major web2py version). This removes the problematic
>> dependency.
>>
>> The second issue is that the repository contains all the applications
>> (admin, examples, welcome). This means I have all those applications on all
>> my productive systems when I install web2py. My options are now to either
>> delete those applications after installing web2py or block them (in the
>> webserver config). I understand web2py comes Batteries included but for
>> real world projects this is not optimal.
>>
>> * Solution: make an own repository for the web2py applications and
>> package them in the available downloads (as you currently already do with
>> DAL in the zip-file).
>>
>> Alex
>>
>>
--
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
---
You received this message because you are subscribed to the Google Groups
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
