On 3/17/17 at 5:53 AM, wpu.cl...@gmail.com (Dan Clark) pronounced:
Got stuck and then unstuck, but there are questions.
First, AWS's EB linux instances are redhat-ish
[ec2-user@ip-172-31-4-9 ~]$ cat /etc/*-release
NAME="Amazon Linux AMI"
VERSION="2016.09"
ID="amzn"
ID_LIKE="rhel fedora"
On Friday, March 17, 2017 at 1:49:19 PM UTC-4, tonthon wrote:
>
> Have you tried https://github.com/elliotpeele/pyramid_oauth2_provider ?
> It seems to miss some use cases but it covers quite well the oauth2
> workflow
>
This looks a lot like my oauth1 solution.
--
You received this
Have you tried https://github.com/elliotpeele/pyramid_oauth2_provider ?
It seems to miss some use cases but it covers quite well the oauth2 workflow
Le 15/03/2017 à 02:01, Jonathan Vanasco a écrit :
> We do the same thing.
>
> A few notes:
>
> * I run the authorization API as a standalone
> On Mar 17, 2017, at 03:53, Dan Clark wrote:
>
> Got stuck and then unstuck, but there are questions.
>
> First, AWS's EB linux instances are redhat-ish
>
> [ec2-user@ip-172-31-4-9 ~]$ cat /etc/*-release
> NAME="Amazon Linux AMI"
> VERSION="2016.09"
> ID="amzn"
>
Thanks for the heads up on activate. I relied on that script quite a bit.
--Dan
On Thu, Mar 16, 2017 at 12:09 AM, Steve Piercy
wrote:
> When I see things like the following, I smell trouble:
>
> (venv)[ec2-user@ip-172-31-13-110 ~]$ virtualenv -p python3 deprecation
Got stuck and then unstuck, but there are questions.
First, AWS's EB linux instances are redhat-ish
[ec2-user@ip-172-31-4-9 ~]$ cat /etc/*-release
NAME="Amazon Linux AMI"
VERSION="2016.09"
ID="amzn"
ID_LIKE="rhel fedora"
VERSION_ID="2016.09"
PRETTY_NAME="Amazon Linux AMI 2016.09"
thanks for sharing those points.
I'm not sure how to transform the existing app. I'll have to clean the
base code a bit before passing to implementing this part.
I'll surely have more questions later on.
Le 15/03/2017 à 02:01, Jonathan Vanasco a écrit :
> We do the same thing.
>
> A few notes:
>