zcopleys-statusnet-clone | A mirror of http :
kandi X-RAY | zcopleys-statusnet-clone Summary
kandi X-RAY | zcopleys-statusnet-clone Summary
zcopleys-statusnet-clone is a PHP library. zcopleys-statusnet-clone has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.
StatusNet is a Free and Open Source microblogging platform. It helps people in a community, company or group to exchange short (140 characters, by default) messages over the Web. Users can choose which people to "follow" and receive only their friends' or colleagues' status messages. It provides a similar service to sites like Twitter, Google Buzz, or Yammer. With a little work, status messages can be sent to mobile phones, instant messenger programs (GTalk/Jabber), and specially-designed desktop clients that support the Twitter API. StatusNet supports an open standard called OStatus that lets users in different networks follow each other. It enables a distributed social network spread all across the Web.
StatusNet is a Free and Open Source microblogging platform. It helps people in a community, company or group to exchange short (140 characters, by default) messages over the Web. Users can choose which people to "follow" and receive only their friends' or colleagues' status messages. It provides a similar service to sites like Twitter, Google Buzz, or Yammer. With a little work, status messages can be sent to mobile phones, instant messenger programs (GTalk/Jabber), and specially-designed desktop clients that support the Twitter API. StatusNet supports an open standard called OStatus that lets users in different networks follow each other. It enables a distributed social network spread all across the Web.
Support
Quality
Security
License
Reuse
Support
zcopleys-statusnet-clone has a low active ecosystem.
It has 1 star(s) with 0 fork(s). There are 1 watchers for this library.
It had no major release in the last 6 months.
zcopleys-statusnet-clone has no issues reported. There are no pull requests.
It has a neutral sentiment in the developer community.
The latest version of zcopleys-statusnet-clone is current.
Quality
zcopleys-statusnet-clone has no bugs reported.
Security
zcopleys-statusnet-clone has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
zcopleys-statusnet-clone is licensed under the AGPL-3.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
zcopleys-statusnet-clone releases are not available. You will need to build from source code and install.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of zcopleys-statusnet-clone
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of zcopleys-statusnet-clone
zcopleys-statusnet-clone Key Features
No Key Features are available at this moment for zcopleys-statusnet-clone.
zcopleys-statusnet-clone Examples and Code Snippets
No Code Snippets are available at this moment for zcopleys-statusnet-clone.
Community Discussions
No Community Discussions are available at this moment for zcopleys-statusnet-clone.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install zcopleys-statusnet-clone
Installing the basic StatusNet Web component is relatively easy, especially if you’ve previously installed PHP/MySQL packages.
Unpack the tarball you downloaded on your Web server. Usually a command like this will work: tar zxf statusnet-0.9.6.tar.gz ...which will make a statusnet-0.9.6 subdirectory in your current directory. (If you don't have shell access on your Web server, you may have to unpack the tarball on your local computer and FTP the files to the server.)
Move the tarball to a directory of your choosing in your Web root directory. Usually something like this will work: mv statusnet-0.9.6 /var/www/statusnet This will make your StatusNet instance available in the statusnet path of your server, like "http://example.net/statusnet". "microblog" or "statusnet" might also be good path names. If you know how to configure virtual hosts on your web server, you can try setting up "http://micro.example.net/" or the like.
Make your target directory writeable by the Web server. chmod a+w /var/www/statusnet/ On some systems, this will probably work: chgrp www-data /var/www/statusnet/ chmod g+w /var/www/statusnet/ If your Web server runs as another user besides "www-data", try that user's default group instead. As a last resort, you can create a new group like "statusnet" and add the Web server's user to the group.
You should also take this moment to make your avatar, background, and file subdirectories writeable by the Web server. An insecure way to do this is: chmod a+w /var/www/statusnet/avatar chmod a+w /var/www/statusnet/background chmod a+w /var/www/statusnet/file You can also make the avatar, background, and file directories writeable by the Web server group, as noted above.
Create a database to hold your microblog data. Something like this should work: mysqladmin -u "username" --password="password" create statusnet Note that StatusNet must have its own database; you can't share the database with another program. You can name it whatever you want, though. (If you don't have shell access to your server, you may need to use a tool like PHPAdmin to create a database. Check your hosting service's documentation for how to create a new MySQL database.)
Create a new database account that StatusNet will use to access the database. If you have shell access, this will probably work from the MySQL shell: GRANT ALL on statusnet.* TO 'statusnetuser'@'localhost' IDENTIFIED BY 'statusnetpassword'; You should change 'statusnetuser' and 'statusnetpassword' to your preferred new username and password. You may want to test logging in to MySQL as this new user.
In a browser, navigate to the StatusNet install script; something like: http://yourserver.example.com/statusnet/install.php Enter the database connection information and your site name. The install program will configure your site and install the initial, almost-empty database.
You should now be able to navigate to your microblog’s main directory and see the "Public Timeline", which will be empty. If not, magic has happened! You can now register a new user, post some notices, edit your profile, etc. However, you may want to wait to do that stuff if you think you can set up "fancy URLs" (see below), since some URLs are stored in the database.
Unpack the tarball you downloaded on your Web server. Usually a command like this will work: tar zxf statusnet-0.9.6.tar.gz ...which will make a statusnet-0.9.6 subdirectory in your current directory. (If you don't have shell access on your Web server, you may have to unpack the tarball on your local computer and FTP the files to the server.)
Move the tarball to a directory of your choosing in your Web root directory. Usually something like this will work: mv statusnet-0.9.6 /var/www/statusnet This will make your StatusNet instance available in the statusnet path of your server, like "http://example.net/statusnet". "microblog" or "statusnet" might also be good path names. If you know how to configure virtual hosts on your web server, you can try setting up "http://micro.example.net/" or the like.
Make your target directory writeable by the Web server. chmod a+w /var/www/statusnet/ On some systems, this will probably work: chgrp www-data /var/www/statusnet/ chmod g+w /var/www/statusnet/ If your Web server runs as another user besides "www-data", try that user's default group instead. As a last resort, you can create a new group like "statusnet" and add the Web server's user to the group.
You should also take this moment to make your avatar, background, and file subdirectories writeable by the Web server. An insecure way to do this is: chmod a+w /var/www/statusnet/avatar chmod a+w /var/www/statusnet/background chmod a+w /var/www/statusnet/file You can also make the avatar, background, and file directories writeable by the Web server group, as noted above.
Create a database to hold your microblog data. Something like this should work: mysqladmin -u "username" --password="password" create statusnet Note that StatusNet must have its own database; you can't share the database with another program. You can name it whatever you want, though. (If you don't have shell access to your server, you may need to use a tool like PHPAdmin to create a database. Check your hosting service's documentation for how to create a new MySQL database.)
Create a new database account that StatusNet will use to access the database. If you have shell access, this will probably work from the MySQL shell: GRANT ALL on statusnet.* TO 'statusnetuser'@'localhost' IDENTIFIED BY 'statusnetpassword'; You should change 'statusnetuser' and 'statusnetpassword' to your preferred new username and password. You may want to test logging in to MySQL as this new user.
In a browser, navigate to the StatusNet install script; something like: http://yourserver.example.com/statusnet/install.php Enter the database connection information and your site name. The install program will configure your site and install the initial, almost-empty database.
You should now be able to navigate to your microblog’s main directory and see the "Public Timeline", which will be empty. If not, magic has happened! You can now register a new user, post some notices, edit your profile, etc. However, you may want to wait to do that stuff if you think you can set up "fancy URLs" (see below), since some URLs are stored in the database.
Support
The primary output for StatusNet is syslog, unless you configured a separate logfile. This is probably the first place to look if you’re getting weird behaviour from StatusNet. If you’re tracking the unstable version of StatusNet in the git repository (see below), and you get a compilation error ("unexpected T_STRING") in the browser, check to see that you don’t have any conflicts in your code. If you upgraded to StatusNet 0.9.x without reading the "Notice inboxes" section above, and all your users' 'Personal' tabs are empty, read the "Notice inboxes" section above.
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page