Kodi by default dont give the icon from programme in channels list. So, it’s not perfect but a simple workaround do the ugly job. This example use a 600×372 image.
First of all, install Skin Helper Service from kodi repository.
Then set two triggers on epg file Kodi\userdata\Database\Epg11.db:
|
CREATE TRIGGER t_icon AFTER INSERT ON epgtags FOR EACH ROW BEGIN UPDATE epgtags SET sPlotOutline = NEW.sIconPath WHERE idBroadcast = NEW.idBroadcast; END CREATE TRIGGER t_iconu AFTER UPDATE ON epgtags FOR EACH ROW BEGIN UPDATE epgtags SET sPlotOutline = NEW.sIconPath WHERE idBroadcast = NEW.idBroadcast; END |
With this, the sIconPath field will be copy to sPlotOutline field. This field isn’t used in IPTV Simple Addon but Kodi sends the var to skin in channels list.
Now we need to show the image in kodi skin. In this example we will use the defaut skin from Kodi 17 – Estuary.
Add the control image before the plot with the PlotOutline field:
|
<control type="image"> <left>100</left> <top>360</top> <width>600</width> <aspectratio align="right" aligny="top">keep</aspectratio> <texture fallback="DefaultTVShows.png">$INFO[Listitem.PlotOutline]</texture> <fadetime>200</fadetime> </control> |
Change the plot position to bottom of image:
|
<control type="textbox"> <top>750</top> <width>820</width> <bottom>114</bottom> <label>[B]$INFO[ListItem.EpisodeName,,[CR]][/B]$INFO[ListItem.Plot]</label> </control> <control type="textbox"> <top>750</top> <width>800</width> <height>362</height> <align>center</align> <font>font27</font> <textcolor>80FFFFFF</textcolor> <label>$LOCALIZE[19055]</label> <visible>String.IsEmpty(Listitem.Plot)</visible> </control> |
Now the result:

Checkout for the current folder
|
svn co file:///var/svn/project/trunk . |
Ignore multiple files/dirs.
If you want to ignore tmp,obj,bin dirs and all files with *.o*.lib,*.la extension. Save this file
and name it svnignore.txt, the following command will do the job !
|
svn propset svn:ignore -F svnignore.txt . |
If one of your directories is already under version control, remove it first with:
…then ignore:
|
svn propset svn:ignore tmp . |
Add files to commit in full depth
|
svn --force --depth infinity add . |
Clean log files like mysqld-bin.000001:
|
mysql> FLUSH LOGS; mysql> RESET MASTER; |
That command should read
Code:
|
ssh -i /path/to/your/privatekey your_username@yourdomain.com |
To use sshfs you need to install the package, the command to install it is
Code:
|
sudo apt-get install sshfs |
then to mount a remote host as the directory /mnt (your mount point) (you can use any directory you like even ones with stuff in – it will not write over the top of them the contents will just be invisible until you umount). Note the -o ssh_command… option should not be necessary if you have loaded your key using ssh-add /path/to/your/privatekey .
Code:
|
sshfs username@remotehost.com:/folder/in/remotehost /mnt -o ssh_command='ssh -i /path/to/your/privatekey' |
to unmount where /mnt is your mount point:
I prefer to use a mount point in my home directory. e.g. /home/username/mnt/ and use that as my mountpoint instead
Source of this great guide: The Web Development Logs – http://webdevlogs.blogspot.pt/
This setup guide is written for a single server installation, using Apache, MySQL and PHP to keep things simple.
I make no excuses that i borrowed a lot of content from the original Adobe Content Server 4 Technical Reference Manuals and other Documentation while adding in my personal notes, screen shots, and potential pitfalls to look out for.
Read through everything you can before beginning the setup process, understanding the concept of Adobe Content Server as a whole is as important as getting everything running smoothly.
Please refer to, study, and read the original ACS4 installation and quick start documentation here.
The ACS4 installation can be split into steps:
- Installing the basic requirements
- Setting up the Admin console
- Setting up the Fulfillment service
- Setting up the Packaging service
- Generating the Certificate files
- Completing Config Files
- Content Server Status Checks
- Book Packaging and Distribution
- Serving the Sample Store
You may wish to have the packaging service and media storage on seperate machines to distribute workloads.
Basic requirements to run Adobe Content Server:
- The Java Runtime Environment (JRE)
- Apache Tomcat version 6 or higher
- MySQL version 5 or higher.
In addition, to run an online store, you will also need:
- Apache HTTP Server
- PHP 5 or above.
Ler mais…
Multiple ways to add multiple files to svn repository:
|
svn st | grep "^?" | awk '{ print $2}' | while read f; do svn add $f; done |
OR
|
svn add `svn status | grep "^?" | awk '{print $2 }'` |
OR
|
svn add file1 file2 file3 file4 #etc.. |