semillas / semillas_platform Goto Github PK

Responsible of formating properly the phone and calling #50 User.validate_phone

Create endpoint retrieving all categories:

endpoint: GET api/v1/categories

Check: /api/v1/services/all_services

I can provide Godaddy credentials for this.

seems that the other three combinations are working:

• http://semillasocial.org
• http://www.semillasocial.org
• https://www.semillasocial.org

I have this configuartion set up.

Maybe is needed to use deep DNS configuration, but we run in the problem that Heroku just gives you access to herokuapp.semilla.com, and no IP. And Godaddy just allows you to set A (only IP) register types in root (@) dns records.

Every user will have a wallet entity connected. The Wallet model can be taken from this one:
https://github.com/jpanganiban/django-pursed

I think the Transaction model should have also the source wallet of the transaction.

Fields:

• Name
• Photo (like in user model)
• order (integer)

It'd would be a good idea to use modeltranslation app for translating the name: http://django-modeltranslation.readthedocs.io/en/latest/installation.html

Endpoint for the feed of items (posts) the user will see:

-/api/v1/posts/feed -> The feed ordered by the location/publishing time of the user.
- URL parameters:
- Lat: Latitude to order by geolocation
- Lon: Longitude to order by geolocation
- category: Category id to filter by that category
- search: String to search item using that string

The default order should be by distance.

In the future, another get param can be order with two options: distance, recent

This will be shown in the User Profile View. A list of every single service.

Is needed the following URLs:

• /api/v1/user/<user_id>/services -> All the post that user is offering, setting first the active (order by post date), and after this the inactive.

https://django-allauth.readthedocs.io/en/latest/providers.html#facebook

Is needed to use search engines: https://docs.djangoproject.com/en/1.10/ref/contrib/postgres/search/

PhotoService model will have:

• service: foreign key to service (this way we achieve the one to many, many photos can be pointing to one service.
• picture: models.ImageField(null=False, blank=False, ... )

Then they should be added to ServiceSerializer. And return them inside the json in a list ordered by id.
In the photos field. They can be added like in this example: http://www.django-rest-framework.org/api-guide/relations/#nested-relationships

When loading the feed, it should get the user position from the browser.

If the user allows the browser to retrieve it, it will update the user with the coordinates (PATCH /user/) and request the feed again.

It should also update the User with the permission option chosen (Browser not supported, permission denied, permission allowed).

This will call CheckMobi service and verify the user implemented in #58

Parameter: phone properly formated (in the format CheckMobi requires)

• Takes the phone properly formatted from the view
• Saves the phone
• Perform Request to CheckMobi
• Return whether or not the CheckMobi Request was successful

Should be uploaded to S3

Used when a user publish a new service.

http://www.django-rest-framework.org/api-guide/validators/
http://www.django-rest-framework.org/api-guide/parsers/#parsers

A simple test using the functionalities of django rest framework: http://www.django-rest-framework.org/api-guide/testing/

Run tests with:
$ docker-compose -f dev.yml run python manage.py test

More info in: https://docs.djangoproject.com/en/1.10/topics/testing/overview/

To every user not having the browser in English, the web is showing up in Spanish.

So anyone from... France for example opening the web, it will be in Spanish.

Also in order to have the strings inside the code written in English would be great to have the default language as English.

All user movements ordered by date

Use this

https://github.com/stefanfoulis/django-phonenumber-field

phone_verified should be a not null default false boolean.

The View is UserDetail, but I think it's gonna need to be divided between RetrieveUserDetail and UpdateUserDetail

We can use this:

http://www.django-rest-framework.org/tutorial/4-authentication-and-permissions/#object-level-permissions

Contact tab and a part of the team, is not translated.

It'd would be great to have it translated.

After is translated, it should be uploaded to Transifex.

It will be used afterwards in ReactJS to ask for the feed Endpoint to be done here:

#2

Service is a service being offered in the platform or an item being sold.

We need to add a Gallery of photos to the Service model.

validate method will save in Redis the CheckMobi user identifier so verify_pin can retrieve it and perform the verification.

The goal is to encourage people to sign-up in our landing page with the promise of keeping them up to date and notify them as soon as we launch the first version of the product.

So the sign-up should include a text like:
"We are not live yet, but we can keep you updated of our improvements and notify you once we launch"

And the after sign-up page should have a message like:
"Thanks a lot for joining. We will keep you posted. Keep reading about us" And a link to 'people' tab.

https://github.com/marcgibbons/django-rest-framework-docs

There are many string in English regarding each software been used.
Also there are some sentences below "version" title which need a proper tranlation as well.
It would be very nice if they get translated.

https://django-allauth.readthedocs.io/en/latest/providers.html#google

Post Params:

Source: user_uuid
Destination: user_uuid
Quantity: int

This will be called once the user has introduced the 4 digits he got (through SMS or last four digits of lost call).

• Will call verify_pin from #58
• Update phone_verified flag

https://django-allauth.readthedocs.io/en/latest/providers.html#openid

Due to the match of technologies to use we should get inspired by:

https://github.com/iesteban/channel_chat

Avoiding the group chat.

Notes: Check out authentication.

Comes from #8 (comment) :

@iesteban says:

For the development environment, the approach I like the most is to create a script like populate_development_database. Which will be called every time we start the development environment.

That script, let's call it pre_start.py for example, will check there is an entry of a Facebook Provider in database and create if it's not there. Something like:

if not SocialApp.objects.filter(provider=Facebook):
facebook_provider = SocialApp(
provider=Facebook,
secret_key= '34567890',
...
)
facebook_provider.save()

And the place too call pre_start.py will be here: https://github.com/Semillas/semillas_backend/blob/master/compose/django/gunicorn.sh#L2

This will set the development key public. I think there is no problem at all. But maybe we should research a little bit.

This will be called once the user has got the confirmation code.

Will call pin_verify method implemented in #58

Will return whether or not it was verified.

Param Url:

user: user_uuid