PyLucid CMS Logo

blog

tag cloud ajax | Amazon | Apache | Aptana | backward incompatible | blog | browser | bugfix | ColorMirror | creole | database | dbtemplates | development | django | django-reversion | django-sync | django-sync-server | django-tagging | django-tools | django-weave | DjangoBB | documentation | dokumentation | Eclipse | editor | encoding | fastcgi | firefox | firefox sync | formset | generic | git | gunicorn | honypot | html | HTML dump | include | IRC | javascript | JS-SHA-Login | linux | login | mysql | nginx | pip | plugin | politik | pydev | pygments | pylucid | pypy | python | release | screencast | screencasts | security | server | sicherheit | software | sqlite | standalone | suchmaschine | svn | test | textile | unittest | v0.10 | v0.11 | virtualenv | visible changes | web | webspace

↑ March 1, 2014 - Switch the PyLucid base to a other CMS?  #

Before 8 months published by jens.

Time is money... PyLucid CMS need more man power, more time and there is only a small contribution in the past. So everything always takes forever. Currently the django 1.6 migration...

That's why I ask me to change the base system of PyLucid with a other django based CMS? But if so, then what project?

At least the list at https://www.djangopackages.com/grids/g/cms/ looks a little long.

As a limiting criterion: The CMS should have content versioning. Would be fine if django-reversion would be used (So i can use my https://github.com/jedie/django-reversion-compare )

Seems that django-reversion used only this (big enough and under active development):

django-cms https://github.com/divio/django-cms
Feincms https://github.com/feincms/feincms

django-page-cms should also be able to versioning. But it's unclear how this is done. see: https://github.com/batiste/django-page-cms/issues/94

Discuss in our forum, here: http://www.pylucid.org/de/forum/topic/366/ (en)

(Last update: March 1, 2014, 5:15 p.m. by jens.)

tags development | pylucid
0 comments...

↑ Sept. 30, 2013 - v1.5.1: https login  #

Before 1 year, 1 month published by jens.

v1.5.1 changes:

  • Update bootstrap script
  • protect normal users via JavaScript to submit login data into honeypot
  • Add "https" option in auth db-preferences

↑ https option  #

If your side is also available via https, then you can force the usage of secure http JS-SHA-Login by changing auth db preferences:

  • Django Admin Site / Dbpreferences / Preferences / AuthPreferencesForm
  • activate the 'Https urls' checkbox

If https urls is activate, the use will be redirected if the clicked on the login link.

diff view: https://github.com/jedie/PyLucid/compare/v1.5.0...v1.5.1

(Last update: Sept. 30, 2013, 2:49 p.m. by jens.)

tags development | pylucid | visible changes
0 comments...

↑ Aug. 7, 2013 - PyLucid env mit PyPy erstellen...  #

Before 1 year, 2 months published by jens.

Hier mal die Zeilen, um ein PyLucid mit PyPy zu erstellen:

Bash
 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11
12
13
14
# In diesem beispiel ist es die 32Bit Version von PyPy:
~$ wget https://bitbucket.org/pypy/pypy/downloads/pypy-2.1-linux.tar.bz2
~$ tar xfv pypy-2.1-linux.tar.bz2

# Mal testen, ob PyPy läuft:
~$ ./pypy-2.1/bin/pypy --version
Python 2.7.3 (480845e6b1dd, Jul 31 2013, 11:05:31)
[PyPy 2.1.0 with GCC 4.4.3]

# PyLucid bootstrap:
~$ wget --timestamp https://raw.github.com/jedie/PyLucid/master/bootstrap/pylucid-boot.py

# env mit PyPy erzeugen:
~$ ./pypy-2.1/bin/pypy pylucid-boot.py PyLucid_pypy_env

Dann erzeugt man eine sog. page instance, wie in der PyLucid Doku beschrieben.

Damit manage.py, index.fcgi funktionieren und den PyPy interpreter nehmen, muß man die shebang Zeile anpassen, z.B.:

Diff
1
2
-#!/usr/bin/env python
#!/home/FooBar/PyLucid_pypy_env/bin/pypy
tags pylucid | pypy | python | virtualenv
0 comments...

↑ July 25, 2013 - django 1.5 support in PyLucid  #

Before 1 year, 3 months published by jens.

We started the update process to switch from Django 1.4.x to Django 1.5.x

For the development phase we done everything in a separate branch: django1.5
github compare view:

All PyLucid own projects would also have a django1.5 branch in development phase.

We use the step to change a few things in PyLucid:

  • PluginPage urls would be inserted into the global urls.py (So plugin urls.py are usable everywhere)
  • Plugin API change a little bit: The way how request.PYLUCID would be created:
    • New @pylucid_objects decorator for plugin views the get request.PYLUCID

(Last update: July 25, 2013, 11:01 a.m. by jens.)

tags development | django | pylucid | visible changes
0 comments...

↑ July 18, 2013 - PyLucid auf Uberspace.de installieren...  #

Before 1 year, 3 months published by jens.

Es gibt nun eine Übersicht, wie man PyLucid bei Uberspace.de installieren kann:

Im Groben ist es sehr ähnlich wie in der normalen PyLucid installations Anleitung. Aber lest selber ;)

(Last update: July 18, 2013, 8:21 a.m. by jens.)

tags documentation | pylucid | webspace
0 comments...

↑ July 18, 2013 - install docu cleanup  #

Before 1 year, 3 months published by jens.
tags documentation | pylucid
0 comments...

↑ May 24, 2013 - New in PyLucid v1.5.0  #

Before 1 year, 5 months published by jens.

The main goals of this release: With v1.5.0 every PyLucid user can change this password without a password email reset. Even normal, non-stuff users.

There is a new menu point:

  • PyLucid Admin Menu / tools / user profile

This "user profile" page display a few information (Maybe we add more in the future). There are two links:

  1. JavaScript enhanced password change
  2. Normal password set view from django.

The second one is only as fallback, because then you send your password in plaintext (without https)!
The first one builds the salted hashed direclty in the browser!

↑ backward incompatible  #

We change the slat length from 5 to 12 characters. So if you don't use SQLite you need a database schema migration, so that the field UserProfile.sha_login_salt changes the max length.

↑ migrate database changes  #

Bash
1
2
# Do south migrations
/var/www/YourSite$ ./manage.py migrate

In the output you must see theses lines:

Bash
1
2
3
4
5
...
Running migrations for pylucid:
 - Migrating forwards to 0004_salt_length.
 > pylucid:0004_salt_length
...

↑ install plugin view  #

You must also reinstall the PyLucid plugins, to activate the new user profile admin view. Just click on:

  • PyLucid Admin Menu / PyLucid / install plugins

Compare v1.4.3...v1.5.0 diff. (Note: v1.4.4 was not really a release!)

(Last update: May 24, 2013, 10:17 p.m. by jens.)

tags backward incompatible | development | pylucid | visible changes
0 comments...

↑ Nov. 20, 2012 - New in PyLucid v1.4.2  #

Before 1 year, 11 months published by jens.

Some bugfixes and a new flickr functionality added in v1.4.2:

More information about the flickr stuff is in the documentation page. Some examples are here:

tags development | pylucid | visible changes
0 comments...

↑ Oct. 18, 2012 - static HTML dump  #

Before 2 years published by jens.

We started a django management command to create a static HTML dump of a web page:

So it should be possible to create a snapshot of your complete site to e.g. put it via FTP on a second web server or to a sub-domain etc.

To create a dump e.g.:

Bash
1
/var/www/YourSite$ ./manage.py html_dump /var/www/static_dump/

To test the snapshot you can run a simple HTTP server e.g.:

Bash
1
2
3
/var/www/YourSite$ cd /var/www/static_dump/
/var/www/static_dump$ python -m SimpleHTTPServer
Serving HTTP on 0.0.0.0 port 8000 ...

Note: Don't use this server in production ;)

(Last update: Oct. 18, 2012, 2:39 p.m. by jens.)

tags development | HTML dump | pylucid
0 comments...
Syndication feed format:
0 comments for 'blog':
    there exist no comment for 'blog'
Leave a comment
tag navi developing

django-processinfo: 6.9 ms of 1255.6 ms (0.5%)